super-ship
Audit, fix, sweep, then ship it all at once
The super-ship skill chains four others: drift-audit, api-consistency, responsive-sweep and ship. It owns only the rules for how they connect. Asking for it is the owner’s yes to fix drift and deploy, but not to change the published contract. Below are the steps, then one structural change traced from its branch to the live site. The full skill file is on Skills.
The steps
- Check the change is structuralA moved folder, a new build step, a renamed surface. For a copy fix or a single component, the skill says so and offers plain ship instead.
- Run the drift auditEvery section of
drift-audit, not a lighter pass. If any section was skipped or narrowed, the flow stops and asks before going on. - Run the API audit
api-consistencyover each component the diff touched, plus its family. It widens to the whole library only for a library-wide change. - Fix what is broken or staleDrift is repaired in the session. A rename, a new prop or a new deprecation changes the published contract, so it stops and asks. Gaps and judgement calls are reported, not acted on.
- Re-check the fixesRun
npm run validate-registryagain, so a fix cannot add a broken reference, and repeat the API audit over any component a fix changed. - Sweep every page
responsive-sweepruns against a build of the combined tree, every route at every width. A break with one right answer is fixed. A proposed acceptance waits for the owner. - ShipThe ship flow from its first step: the full verify, separate commits for the work and each set of fixes, the merge into main, the push, CI watched to green, and the live site proven rendering.
- ReportOne message: the audit with its coverage table, the API findings, the sweep, what shipped and what is left as a follow-up.
A structural change, end to end
The work waits on its branch while the audits read the repo. The fixes join it before the full verify, so the push carries the change and everything that describes it.
1 · Auditreads, changes nothing
2 · Fix and sweeppre-approved repairs
3 · Shipthe ship flow, from its step 0
4 · Liveproven, not assumed
Session worka structural change on a branch
Drift auditevery section · .claude/skills/drift-audit/
Coverage gatea skipped section stops the flow
API auditapi-consistency · components the diff touched
Follow-upsgaps and new validators, reported only
Drift fixesbroken and stale findings
Re-checknpm run validate-registry
Responsive sweepscripts/check-responsive-layout.mjs
Sweep fixesbreaks with one right answer
Stops to askcontract changes · judgement calls · acceptances
Full verifynpm run verify
Separate commitswork · drift fixes · sweep fixes
Merge into mainthen push
GitHub Actions CI.github/workflows/ci.yml
Vercela push to main deploys
Live hydration smokescripts/smoke-hydration.mjs
Combined reportaudit · API · sweep · ship
contract changeswith the session workpush to mainZoom outZoom inFit the whole mapExpand the map
What each finding does
Invoking the skill approves repairs and the deploy. Anything past that waits for the owner.
| Finding | What happens | Result |
|---|---|---|
Broken or stale prose | Repaired in the session | Fixed |
API drift, such as a stale description | Repaired, since no consumer’s code changes | Fixed |
Layout break with one right answer | Repaired at its source | Fixed |
Rename, new prop or new deprecation | Waits, since the version is the owner’s call | Asks |
Skipped audit section | Waits for the owner to accept a narrow audit | Asks |
Proposed sweep acceptance | Waits, since it hides the finding for good | Asks |
Judgement call | Waits rather than resolving it silently | Asks |
Gap or new validator | Listed as a follow-up | Reported |
The validator chain itself broken | Ends the whole flow with a report | Stops |