All commands
Command
/report-bug
structured upstream bug reports
Turn a live Shipmates failure into a structured upstream issue.
See it run
/report-bug runs, in order.How to run it
Run it in your harness
/report-bug [symptom text] [apply] — default report-only preview; apply files on saman-mb/shipmates after captain approval<angle brackets> = required · [square brackets] = optional
How it works
Capture
Record what broke, which harness, which command, and the expected vs observed result.
No specialist — the run harvests context from the session.
Dedupe
Search existing upstream issues so a duplicate is a comment, not a new ticket.
Still the run — no spawn until the draft.
Draft
Shape a title and body a maintainer can act on.
Always
Also sit when
technical-writerthe report cites command-spec behaviour
File
Preview first; create the GitHub issue only when you say apply.
No extra spawn — you confirm, then it files.
When to use
- Shipmates itself misbehaved and maintainers need a triage-ready report.
- Fixing your own repo? /shipmates-fix-bug. Cleaning a backlog? /consolidate-issues.
The skill
The installer ships the full skill — stages, gates, config — from commands/report-bug.md.