From jon-skills
Implement one AFK local issue end-to-end with TDD, subagent-assisted context control, review fixes, scoped architecture improvements, issue updates, checks, and an automatic commit. Use when the user asks to ship, implement, complete, or run an issue file from docs/issues/.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jon-skills:ship-issueThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Implement exactly one local issue file from `docs/issues/` without handholding.
Implement exactly one local issue file from docs/issues/ without handholding.
AFK.HITL, stop immediately and say it needs a design/grilling pass.CONTEXT.md, ADRs, tests, and existing code.Parent section.git status --short and record pre-existing dirty files.Do not broaden the issue. If work is bigger than the issue, ship the smallest valid slice and create follow-up issues for the rest.
Main agent owns scope, edits, tests, staging, and commit. Use subagents only for bounded side work: explorer for context scouting, review, or architecture scouting; worker only for a disjoint patch with explicit file ownership.
Do not delegate the immediate blocker or duplicate work. Integrate subagent results yourself and discard anything outside issue scope.
Use the ../tdd/SKILL.md workflow: one public behavior test, expected failure, minimum implementation, repeat, then refactor only while green.
Prefer tests that survive refactors. Avoid internal mocks unless the public seam is an external dependency.
Look for bugs, regressions, missing tests, and risky assumptions. Fix every valid finding and rerun affected tests after each fix group.
Use ../improve-codebase-architecture/SKILL.md. Implement improvements when they:
If an opportunity exceeds this blast radius, create a follow-up issue and link it from the current issue. Run a second review pass after architecture changes.
Before committing, targeted tests, added/changed tests, nearest suite, and clear format/lint/typecheck commands must pass.
Run the full suite when documented or reasonably bounded. If required checks cannot pass, stop before staging or committing and report the blocker.
## Implementation Notes with brief assumptions, design notes, and any
follow-up issue links.## Verification with the exact commands that passed.## Status with Complete in this commit.Stage only changes made for this issue. Never stage unrelated pre-existing dirty files.
Use ../commit/SKILL.md to create the commit with a
meaningful Conventional Commits body, Tested: trailers, and Refs: pointing to
the issue file.
npx claudepluginhub jonbito/skillsCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.