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.

Problem

What problem this solves

Bug work often oscillates between overreacting with a rushed patch and overcomplicating a local issue that could have been fixed directly.

Outcome

What changes when it works

You get a clearer decision about whether the issue should be fixed now, investigated further, or routed into a stronger contract path, using the bug dossier as the working record.

Why It Matters

What this changes for a solo founder

This skill helps you move quickly without pretending every bug is trivial. It keeps speed and judgment in the same loop, and it keeps the diagnosis attached to the bug itself.

When to use it

When the starting point is a concrete bug report or failing behavior
When it is unclear whether the issue is truly local
When a bug may hide a deeper product or permission problem

What you give it

The observed bug, error, or failing flow
Any relevant expected behavior if known

What you get back

A triage decision and rationale
Either a direct-fix path or a spec-first reroute
A bug-dossier-driven fix loop when BUG-ID is provided
A durable bug record even when the fix starts as a direct local patch, except for explicit minor exceptions
A route to sg-browser when the bug needs non-auth browser evidence
A sharper understanding of the real bug boundary

Typical examples

/sg-fix users can still access archived projects
/sg-fix dashboard crashes on first login
/sg-fix checkout spinner never resolves

Limits

It is for bounded bug work, not broad redesign
Some bug reports still need deeper clarification before safe implementation
When a bug id is supplied, the skill consumes shipglows_data/workflow/bugs/BUG-ID.md and appends diagnosis and fix attempts there instead of relying on chat history

Related Skills

See the rest of the loop around this move.

Plan & Decide

sg-spec

Turn a fuzzy request into an implementation-ready contract before code starts mutating the repo.

The spec-writing skill for shaping non-trivial work into a clear user story, behavior contract, executable task list, and chantier history.

Open skill page

Build & Fix

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.

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

Build & Fix

sg-start

Start implementation when the task is ready, and force a stronger path when it is not.

The main execution entrypoint for beginning real work after the problem and contract are clear enough, while keeping the chantier flow visible.

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

Go 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.

Documentation Overview Open skills on GitHub Return to the skills hub