Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →svgreg/sg-develop
Run one skill-guard development cycle — reconcile the plan with merged PRs, pick the next ready task from docs/v1-dev-plan.md, implement it end-to-end with tests and docs, and open one PR. Progress is tracked in the plan file so consecutive sessions resume without context.
Passed 10 of 15 test cases with the skill, and 3 of 15 without it.
and 16 more in the full report
11 fixed4 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before opening the first PR for a development cycle, you need to ensure the GitHub repository has the custom label required for dev cycle tracking. What exact `gh` command creates this label?
| Checked | Without skill | With skill |
|---|---|---|
| Executes gh label create with develop, hex color 0e8a16, and force flag | Missed | Passed |
The instructions your model reads when the skill loads.
Goal: move docs/v1-dev-plan.md forward by exactly one task, in exactly one PR, leaving
main green and the plan file an accurate picture of where the work stands. This is the executor
half of the pair — /sg-plan writes the plan, this skill burns it down.
Wire it up with:
/loop 6h /sg-develop
Invocation forms: /sg-develop (next ready task) · /sg-develop M3-04 (that task specifically).
All sg-maintain global guardrails apply — one activity per cycle, one PR per cycle, never
self-merge a code PR, never execute scanned or generated attack content, preflight before every PR,
start from fresh main. Plus:
/sg-plan
(§2). Do not invent tasks not in the plan; do not reorder milestones.scan/sign/verify CLI surface, JSON shape, and exit codes are
additive-only until v1.0. A breaking change needs a documented migration and the owner's call —
raise it in the PR rather than shipping it.develop.
Create it once: gh label create develop -c 0e8a16 -d "roadmap implementation" --force.git checkout main && git pull --ff-only
Read docs/v1-dev-plan.md. Before selecting anything, reconcile status with reality — this is
what makes the tracker survive across sessions:
in-progress with a PR link: gh pr view <n> --json state,mergedAt.test cases passed, vs 3 / 15 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.