Problem
What problem this solves
Release work often fragments across separate commands, and a green build or pushed commit can be mistaken for proof that the product works live.
Menu Open navigation menu Close navigation menu
Operate & Ship
Skill Detail
sg-deploy
Run the whole release confidence loop instead of stitching checks, ship, prod, browser proof, and verification by hand.
A release orchestration skill for moving work through technical checks, bounded shipping, deployment readiness, post-deploy evidence, final verification, and optional changelog routing.
Outcome
What changes when it works
You get a stricter release loop that names each gate, routes the right proof skill, and keeps unproven behavior visible.
Why It Matters
What this changes for a solo founder
This skill protects the last mile of shipping. It turns release into evidence gathering instead of a vibe check after git push.
When to use it
- When implementation is ready and you want to release the current bounded scope
- When a project needs post-push deployment truth before browser or manual testing
- When you want one report for checks, ship, deployment, evidence, verification, and release notes
What you give it
- The current repository state or a target project
- Optional target environment such as preview or production
- Any explicit skip-check or no-changelog intent
What you get back
- A phased release report
- A route through sg-check, sg-ship, and sg-prod
- Correct post-deploy evidence routing to sg-browser, sg-auth-debug, or sg-test
- A final verification gate before release completion is claimed
Typical examples
- /sg-deploy
- /sg-deploy --preview
- /sg-deploy skip-check
- /sg-deploy https://example.vercel.app
Limits
- It orchestrates release skills; it does not replace sg-ship, sg-prod, sg-browser, sg-auth-debug, sg-test, or sg-verify
- A pushed commit, successful deployment, or 200 OK response is not treated as complete release proof
- It blocks when required evidence or verification is missing
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
Deploys the current bounded release scope through checks, ship, deployment truth, evidence routing, and verification.
Consequence
Stops at the first failing gate instead of overclaiming release readiness.
skip-check
Skips the pre-ship sg-check phase only.
Consequence
The report must preserve the validation gap; ship, prod, evidence, and verify gates still apply.
--preview / --prod
Biases the deployment and evidence target toward preview/staging or production.
Consequence
Production proof stays read-only or reversible unless a risky action is explicitly approved.
no-changelog
Skips optional release-note routing after verification.
Consequence
Does not weaken the deploy, proof, or verification gates.
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 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 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 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-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-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 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-changelog
Turn recent git history into a human-readable changelog instead of leaving progress trapped in commits.
A changelog generation skill for summarizing meaningful project changes in a cleaner public format.
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.