Problem
What problem this solves
Work can get stuck in a half-finished state where the changes are ready locally but never move cleanly through the final shipping step.
Menu Open navigation menu Close navigation menu
Operate & Ship
Skill Detail
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.
Outcome
What changes when it works
You get a more decisive transition from verified local work to committed and pushed changes, with visible handling of linked bug risk.
Why It Matters
What this changes for a solo founder
This skill matters because shipping should be a crisp move, not an endless wobble after the real work is already done, and it should not blur residual bug risk into a false sense of closure.
When to use it
- When the implementation is ready to commit and push
- When you want the fast shipping path instead of a long close-out ritual
- After technical and behavioral validation is already done
What you give it
- A repo with ready-to-ship changes
- The current branch and git state
What you get back
- A cleaner final shipping move
- A shipped, blocked, or skipped-checks signal in the spec's chantier flow when applicable
- A shipping report that keeps linked high or critical bug risk visible
- Less hesitation between done locally and done in git
- A tighter release habit for small workstreams
Typical examples
- /sg-ship
- /sg-ship current branch
- /sg-ship after verify
- /sg-ship ship release notes all-dirty
Limits
- It assumes the work is already ready; it is not a substitute for review or verification
- If the branch is messy or the scope is unclear, earlier workflow steps still matter
- Quick ship mode does not become full verification, and it must not hide linked high or critical bug risk
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 special argument
Runs quick ship mode: lightweight checks when practical, then commit and push.
Consequence
Stages only changes that clearly belong to the current task or the selected shipping scope.
skip-check
Skips the pre-commit checks.
Consequence
The report must say validation was skipped; this is a force-through path, not proof the work is safe.
end la tache / end / fin / close task
Switches from quick ship to full close mode.
Consequence
Adds the formal close-out flow before shipping, including task/changelog bookkeeping when relevant.
all-dirty / ship-all / tout-dirty
Stages the entire dirty Git state in the selected repo after the secret check.
Consequence
Includes modified, deleted, and untracked files even when they were not touched in the current conversation.
Related Skills
See the rest of the loop around this move.
Operate & Ship
sg-check
Run the standard technical checks and fix the obvious issues before you pretend the work is done.
A practical quality gate for typecheck, lint, build, and related technical validation in the current project.
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-prod
Check whether production is actually healthy after a push instead of assuming the deploy tells the truth.
A production verification skill for deployment status, logs, and live health checks after release.
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.