Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/ship
Ship phase. Runs isolated integration test in a fresh worktree, creates a PR with full spec + audit report in the body, watches CI, and auto-fixes failures.
Passed 17 of 20 test cases with the skill, and 12 of 20 without it.
and 4 more in the full report
5 fixed14 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
We added a new CLI flag '--output-format' to our data processing binary, but the README.md usage section still lists old syntax examples that fail when run. Can we proceed to prompt for disposition options?
| Checked | Without skill | With skill |
|---|---|---|
| The response halts shipping until README commands are runnable. | Missed | Passed |
The instructions your model reads when the skill loads.
If topology=multi-module (triage announcement or coordinator spec/plan declaration), read ../references/multi-module.md.
Gates — if any fail, stop here:
- [ ] remains in any relevant plan.../references/quality.md).partial-commit).review the whole diff.
Update docs/ROADMAP.md (if it exists):
[x].archive — for multi-module work, archive module artifacts in their owning repositories first; archive the coordinator last.
If user-visible, add to CHANGELOG Unreleased. Releases move it to a version.
Ask disposition: commit / merge / PR / keep / discard.
For a linked multi-repository implementation whose approved plan already includes linked commits: run the commit protocol (non-coordinators in dependency order, record SHAs as the revision set, coordinator last, shared change-set ID in every commit) when the user chooses commit or previously approved that path — do not re-ask whether commits are in scope. Still never push or open a PR without explicit approval.
If a linked commit fails, report partial-commit, preserve all commits and working trees, and report the exact recovery point.
On merge or PR: clean up worktree, delete local branch.
Roadmap has unchecked milestones? → plan next.
No push or PR without explicit user approval.
test cases passed, vs 12 / 20 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.