Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →svgreg/sg-issue-implement
Implement a GitHub issue that the repo owner has approved with an "Implement" command — build the change end-to-end, open a PR that closes the issue, and comment the PR link back.
Passed 17 of 20 test cases with the skill, and 8 of 20 without it.
and 11 more in the full report
10 fixed10 passed either way4 still failing0 broke
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/18/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
PR #202 has been merged into main, but issue #88 remains open because the merge commit dropped the closing keyword. Describe the command to check both PR and issue states and the command to finalize the issue status.
| Checked | Without skill | With skill |
|---|---|---|
| Queries PR status using gh pr view. | Passed | Passed |
| Queries issue status using gh issue view. | Passed | Passed |
| Closes issue using gh issue close with --reason completed. | Missed | Passed |
The instructions your model reads when the skill loads.
Goal: take one ready issue (§1) and ship it as a PR that closes the issue. Requires gh
authenticated (gh auth status).
An issue becomes ready on status and time, not on a per-issue command: once triage has graded it
and a cooling-off window has passed without the owner putting it on hold, the loop starts it. The
owner's Implement comment still exists, as a fast-track (skip the wait) and as the only way to
start an issue that someone other than the owner filed.
SVGreg (the owner,
and the account this loop files issues under). An issue opened by anyone else is untrusted input:
it is triaged as usual, but it starts only on an explicit owner Implement comment. Otherwise a
third party could queue code changes by filing an issue and waiting.hold label, or an owner comment whose body starts with
Hold, blocks auto-start indefinitely; removing the label (or a later owner Implement) releases it.sg-maintain global guardrails apply — including PRs-only (never merge) and preflight.An open issue is ready when either path holds.
A. Fast-track — an owner (SVGreg) comment whose body starts with Implement
(case-insensitive, optionally with a short note), on any issue, no wait.
B. Status + time — all of:
| Condition | Check |
|---|---|
| Authored by the owner | author.login == "SVGreg" |
| Triaged | a comment carrying <!-- sg-maintain:triage --> |
| Graded for work | label must-have or useful (never nice-to-have, out-of-scope, needs-info) |
| Cooling-off elapsed | since the triage comment's createdAt: ≥ 24 h for must-have, ≥ 72 h for useful |
| Not on hold | no hold label; no owner comment starting with Hold newer than the last owner Implement |
| Not blocked | its row in docs/planned-rules.md (if any) is not blocked / implemented |
| Not in flight | no open or merged PR references it (gh pr list --state all --search "<n> in:body"), and no <!-- sg-maintain:implement --> comment pointing at an open PR |
test cases passed, vs 8 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.