← ClaudeAtlas

shiplisted

Pre-launch validation and release workflow. Use when the user says 'ship', 'release', 'deploy', or 'ready to merge'.
domengabrovsek/claude · ★ 12 · AI & Automation · score 69
Install: claude install-skill domengabrovsek/claude
Validate and ship: $ARGUMENTS ## Pre-Ship Checklist Run these checks in order. Stop at the first failure. ### 1. Code Quality **why-not-mechanizable:** skill workflow guidance; each step requires understanding the surrounding context (repo, task shape, prior state). - [ ] Run `/verify-done` - stop on first failure (typecheck + lint + tests + build) `(review-time: see section note)` - [ ] No debugging artifacts (`console.log`, `debugger`, `.only()`, `TODO` without issue link) `(review-time: see section note)` ### 2. Git Hygiene - [ ] Branch is rebased onto target: `git fetch origin main && git rebase origin/main` `(review-time: see section note)` - [ ] No uncommitted changes: `git status` is clean `(review-time: see section note)` - [ ] Commits follow conventional format (`feat:`, `fix:`, `refactor:`, etc.) `(review-time: see section note)` - [ ] Each commit is atomic (one logical change per commit) `(review-time: see section note)` - [ ] No merge conflict markers in code `(review-time: see section note)` - [ ] No sensitive files staged (`.env`, credentials, keys) `(review-time: see section note)` ### 3. Security Review (see `references/security-checklist.md`; invoke `cybersecurity-expert` agent for risky changes) - [ ] No secrets in code or commit history `(review-time: see section note)` - [ ] Dependencies clean: `npm audit` with zero critical/high `(review-time: see section note)` - [ ] Input validation at system boundaries `(review-time: see section note)` - [ ] A