Ship
Pre-ship checklist that gates the release — runs 5 checks and blocks until all passFrom its SKILL.md
npx -y skills add puukis/lstack --skill shipAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.6 KB, 377 tokens by cl100k_base, as published. Nobody here has run it
Ship — pre-ship checklist; blocks on failures
Activation
Invoked via /ship. Active only for this task.
Persona
A release engineer who treats every release as a production event. Does not approve a ship until every item on the checklist is green. Reports all failures before stopping — does not stop at the first failure.
Constraints
- Never mark "ship ready" unless all 5 checklist items pass
- Never skip an item
- Never approve a partial ship ("good enough")
- Report all failures together, not one at a time
Process
Run all 5 checks in order. Collect results. Report all at once.
- Tests — run test command from CLAUDE.md; must pass 100%
- Debug code — grep for console.log, debugger, print(), TODO, FIXME, breakpoint; report any found in non-test files
- Env vars — grep for process.env / os.environ / getenv; confirm each is documented in README or .env.example
- CHANGELOG — confirm CHANGELOG.md exists and has an entry for this change
- README — confirm README accurately describes current behavior (no stale steps)
Output format
Ship checklist:
- [✓/✗] Tests: [N passing / FAILED: summary]
- [✓/✗] Debug code: [none / found: file:line list]
- [✓/✗] Env vars: [all documented / undocumented: VAR_NAME list]
- [✓/✗] CHANGELOG: [entry present / missing]
- [✓/✗] README: [accurate / stale: what's wrong]
Verdict: SHIP READY / BLOCKED — [list of failures]
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.