Problem
What problem this solves
ShipGlows already has bug capture, fix, retest, verification, and shipping gates, but the operator still has to remember which command comes next and when the loop can continue safely.
Menu Open navigation menu Close navigation menu
Build & Fix
Skill Detail
sg-bug
Run a bug from report to dossier, fix, retest, verification, and ship risk without skipping gates.
A professional bug loop executor that reads bug state and continues through the right ShipGlows owner skills when safe.
Outcome
What changes when it works
The bug loop continues through the right owner skills when safe, or reports the blocked next command based on dossier status, severity, evidence needs, development mode, and ship risk.
Why It Matters
What this changes for a solo founder
This skill keeps bug work from turning into scattered chat memory. It protects speed by making the next action obvious, and it protects quality by refusing unsafe closure.
When to use it
- When you have a BUG-ID and need to know what comes next
- When a bug was fixed but still needs retest or verification
- When you need to decide whether an open bug blocks shipping
- When a fresh bug report needs test, fix, browser evidence, or spec routing
What you give it
- A BUG-ID, bug summary, or mode such as --retest, --fix, --verify, --ship, or --close
- Optional environment or release context when ship risk matters
What you get back
- A dossier-first bug state summary
- Lifecycle continuation through the right owner skill, or a blocked next command when execution cannot continue safely
- A safety check for missing evidence, retest, verification, and high-risk shipping
- A clear distinction between orchestration and the phase skills that mutate records or code
Typical examples
- /sg-bug
- /sg-bug BUG-2026-05-03-001
- /sg-bug --retest BUG-2026-05-03-001
- /sg-bug --ship BUG-2026-05-03-001
Limits
- It orchestrates the bug loop; it does not replace sg-test, sg-fix, sg-auth-debug, sg-browser, sg-verify, or sg-ship
- It does not close bugs without retest evidence or an explicit closed-without-retest exception
- It does not persist raw sensitive evidence
Arguments
Some arguments change the workflow, not just the wording.
These are the argument switches documented for this skill. For the general rule behind skill arguments, read the skill modes tutorial.
no argument
Summarizes actionable bug state from shipglows_data/workflow/BUGS.md and recent dossiers.
Consequence
Continues the highest-priority safe bug action when possible instead of editing records in the master thread.
BUG-ID
Reads shipglows_data/workflow/BUGS.md and shipglows_data/workflow/bugs/BUG-ID.md, then continues based on status and severity when safe.
Consequence
Keeps the dossier as the source of truth.
--retest BUG-ID
Continues through sg-test --retest BUG-ID.
Consequence
Retest evidence stays in the bug dossier and compact trackers.
--ship BUG-ID
Checks whether the bug state blocks clean shipping.
Consequence
Open high or critical bugs stay visible as blocked or partial-risk.
Related Skills
See the rest of the loop around this move.
Build & Fix
sg-test
Guide the human through the real user flow, then turn the result into test evidence and actionable bugs.
A manual QA skill for creating guided test campaigns, capturing structured outcomes, and preserving bug history after implementation.
Open skill page Build & Fix
sg-fix
Triage a bug fast, decide whether it is safe to patch now, and route it correctly.
The bug-first entrypoint for ShipGlows when the work starts from broken behavior instead of a new feature request.
Open skill page Build & Fix
sg-auth-debug
Debug a broken auth flow in a real browser before you start guessing from static code alone.
A browser-level auth diagnosis skill for reproducing login failures, reading local Clerk/Google/Convex/Flutter references, and isolating the exact break point in the flow.
Open skill page Build & Fix
sg-browser
Open a URL in a real browser and verify one observable non-auth objective.
A general browser verification skill for checking public UI, previews, production pages, visible assertions, screenshots, console messages, and network signals without turning every page check into auth debugging or manual QA.
Open skill page Audit & Improve
sg-verify
Check whether the work really satisfies the user story, not just whether the code compiles.
A verification skill for standard readiness or an explicit excellence-focused second pass beyond the task's acceptance criteria.
Open skill page Operate & Ship
sg-ship
Commit and push quickly when the work is actually ready, instead of stretching closure into another vague step.
A shipping skill for moving finished work through the final commit-and-push path and recording the shipping result when a chantier spec is in scope.
Open skill pageGo Deeper
This public page explains the move. The repository explains the execution contract.
Use the public catalog for education and workflow selection. Move to the docs and GitHub when you want the operator-grade execution details behind the skill system.