Command
/shipmates-fix-bug
reproduce → root-cause → fix → prove
Prove the bug with a failing test, fix the cause, prove it gone.
See it run
/shipmates-fix-bug runs, in order.How to run it
Run it in your harness
/shipmates-fix-bug <issue-number or a description of the bug> [optional repro hints]<angle brackets> = required · [square brackets] = optional
How it works
SDET owns the failing test. An engineer (or SRE, if it is a runtime bug) finds the cause and fixes it. Review always includes SDET, product-manager, and principal-engineer.
Reproduce
Write a test that fails on the bug. No fix until that test is red.
Always
Also sit when
site-reliability-engineerit is a runtime or ops failure
Cause
Find the mechanism that produces the symptom — not just the line that crashed.
Always
Also sit when
site-reliability-engineerit is a runtime or ops failure
Fix
Change the smallest thing that addresses the cause. A fresh engineer, not the one who just diagnosed it, will review later.
Crew
Prove
The new test passes, CI is green, and reviewers sign off on the pushed head.
Also sit when
senior-engineera fresh engineer confirms the fix addresses the causesite-reliability-engineerit was a runtime bug — a fresh SRE reviews instead
When to use
- Something is broken and you want red→green proof, not a guess.
- New behaviour? /ship-issue. Same behaviour, new shape? /shipmates-refactor.
The skill
The installer ships the full skill — stages, gates, config — from commands/shipmates-fix-bug.md.