Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kdlbs/pr-fixup
Wait for CI and automated reviews on a PR, fix valid failures and comments in the primary conversation, verify, and push.
Passed 17 of 19 test cases with the skill, and 9 of 19 without it.
and 8 more in the full report
8 fixed9 passed either way2 still failing0 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/20/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
CI failed on PR #77 for workflow run ID 987654. There is a large log output on GitHub Actions. What command should be used to inspect only the failure lines without flooding the transcript?
| Checked | Without skill | With skill |
|---|---|---|
| Runs gh run view with the log-failed flag. | Passed | Passed |
| Wraps the gh run view invocation in scripts/run-quiet gh-run. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this workflow directly in the user-started primary conversation. Do not
launch a verifier, implementer, or other remediation subagent. A read-only
pr-poller is the sole exception: launch it only when the user explicitly asks
to wait for or monitor PR updates. For a cost-controlled workflow, the user may
switch the same conversation to the lower-cost implementation/test model before
starting CI remediation.
Use gh by default; auth or transport errors leave state unknown, never clean.
If gh returns an authentication error such as 401, use the structured GitHub
connector/API fallback for PR, check, and review data. Avoid dumping full
HTML/diffs. Map GraphQL thread IDs to REST comment IDs before replies, and
refresh current-head state after pushes and review aggregation.
If gh auth status reports a stale or invalid credential while gh auth token
returns a usable token, propagate it explicitly to the affected command, for
example GH_TOKEN="$(gh auth token)" scripts/pr-await <PR>; use the same
prefix for scripts/pr-state and gh run calls. Keep the token out of command
output and logs. If token retrieval fails, use the structured connector
fallback instead.
Create a visible checklist:
Before the first GitHub call, obtain any network approval required by the runtime. If the runtime denies access, stop until the user authorizes access.
Run scripts/pr-state --compact <PR> and scripts/pr-resolve list <PR>.
test cases passed, vs 9 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.