Ship issue
End-to-end conductor that drives a single GitHub issue all the way to a merged PR. Chains the issue-workflow skills — sync the base branch, analyze the issue, implement a minimal fix with a test, open a PR, drive CI to green, confirm the merge, run post-merge cleanup, and wrap up. Use to take one issue from a cold start to merged in a single command. Trigger on "ship issue #X", "ship #123", "take #N to merge", "do issue #X end to end", "full issue loop for #N", "run the whole issue #X".From its SKILL.md
npx -y skills add jerseycheese/agent-skills --skill ship-issueAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.4 KB, as published. Nobody here has run it
Ship Issue
Drive a single issue from a cold start to a merged PR and a clean handoff. This is a conductor: each step leans on an existing skill or native control rather than re-implementing it. Apply a minimal, root-cause fix — don't patch a symptom or pad the change past the issue's scope.
Take the issue number from the user (e.g. "ship issue #326"). If they named an issue instead of numbering it, find it:
gh issue list --search "[keywords]" --json number,title | head -5
The loop
-
Pre-flight — sync and locate. Run
git fetch && git status. Get onto the right base branch (developif it exists, elsemain) and up to date. If you're working in a worktree, confirm it's the right one and that its dev server points at it. Never build or test against a stale checkout — that's where most rework comes from. -
Analyze. Run the
analyze-issueskill: fetch the issue, discover existing patterns in the codebase, set scope boundaries, and produce an implementation plan with MVP-level tests. Diagnose the root cause before writing any code. -
Implement. Apply the smallest fix that resolves the root cause. Reuse existing patterns before introducing new ones. Add or update one MVP-level test that actually covers the change — use
tdd-implementfor the test-first loop. Run the test suite and linter locally; never rig a test to pass. -
Open the PR. Push the branch and open a PR that links the issue (
Closes #N). Keep the title and description tight: lead with context, say what changed and why, skip the fluff. If the fix has a visible before/after (a UI or visual bug), embed it per thegithub-screenshotskill's convention rather than describing it in prose alone. -
Drive CI to green. Watch the checks. When something fails, use
ci-fix-with-memoryso you don't repeat a fix that already failed. Re-push until green. If the same failure resists three or more different fixes, stop and summarize — ask whether to skip, defer, or rethink the approach. -
Confirm the merge. Once CI is green and the PR is approved and merged, take "merged" as ground truth — don't re-verify without a concrete reason.
-
Post-merge cleanup. Run the
post-mergeskill: it syncs the base branch, deletes the merged branch and its worktree, closes the linked issue (completion comment and acceptance criteria checked), and scores the best next issue to pick up. -
Wrap up. Run
wrap-it-upto close the chat with a tight summary and a sweep of durable context (memory, plans, status), so the next session — or a parallel agent — can pick up cleanly.
Notes
- Pin a concrete, evaluator-checkable success criterion up front (e.g. a goal like "issue #N acceptance criteria met, PR open, CI green") and let the evaluator decide done, not self-judgment.
- Each step is a thin pointer to a dedicated skill. If a step needs more depth, open that skill directly rather than duplicating its logic here.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most ship operate skills give
Counted across 1,077 of the 1,713 authors here whose files we hold, read 2026-09-06
- Create GitHub releasein 44 of 1077, across 43 files
- Run the test suitein 30 of 1077, across 25 files
- Create and push git tagin 27 of 1077, across 26 files
- Push commits and tagsin 27 of 1077
- Create annotated tagin 25 of 1077, across 22 files
- Ensure working tree is cleanin 24 of 1077
- Check for product marketing context firstin 23 of 1077, across 6 files
- Commit version bump changesin 22 of 1077, across 21 files
- Update CHANGELOG.mdin 21 of 1077, across 20 files
- Structure launch marketing across three channel typesin 20 of 1077, across 5 files
- Commit and tag the releasein 20 of 1077, across 18 files
- Update the CHANGELOG for new releasesin 19 of 1077
Said here and by no other author read
- Run git fetch and git status
- Watch the checks and drive CI to green
- Run post merge cleanup
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.