shipwright
Production-grade Claude Code skills for shipping quality code.
/ship
├── Audit find issues, auto-fix Critical/Major
├── Review code + UX review, fix until gates pass
├── Docs sync documentation, verify accuracy
└── Ship push branch, open PR
↓
your CI/CD deploys after merge
One command. Four quality gates. No silent failures.
Install
Via Claude Code plugin marketplace (recommended)
In any Claude Code session:
/plugin marketplace add cloverink/shipwright
/plugin install shipwright@shipwright
Then invoke any skill with /ship, /push, /review-full, etc.
Alternative install methods
Symlink (for development on this repo itself)
git clone https://github.com/cloverink/shipwright.git
cd shipwright
./scripts/link-skills.sh
Manual copy (into a single project)
# All skills
cp -r skills/* /path/to/your-project/.claude/skills/
# Or pick individual ones
cp -r skills/ship /path/to/your-project/.claude/skills/
# List every shipped skill (sanity check)
./scripts/list-skills.sh
Skills
All 12 skills live flat under skills/ for easy discovery. Sorted below by /ship pipeline order, then standalone utilities.
| Skill | Phase | Model | What it does |
|---|
/ship | — | Opus | Full A→R→D→S pipeline orchestrator with gate enforcement |
/audit-full | A | Sonnet | Branch-aware audit: whole-project on main, diff-scoped on feature |
/review-full | R | Sonnet | Auto-detect scope (FE/BE/both), dispatch to code + UX review |
/review-code-fix | R | Opus | Code review → fix loop (max 3 rounds, gate >9/10) |
/review-ux-fix | R | Opus | UX review → fix loop (max 3 rounds, gate 10/10) |
/update-docs | D | Sonnet | Sync documentation with code changes |
/review-docs | D | Opus | Verify doc updates are accurate (binary pass/fail gate) |
/push | S | Sonnet | Smart commit + push + auto-create PR (blocks push to main) |
/merge-pr | post-merge | Haiku | Wait for CI → squash merge → cleanup branch |
/parallel-builder | — | Sonnet | Build multiple files in parallel, conflict-free coordination |
/frontend-design | — | Opus | Distinctive UI design (rejects generic AI aesthetics) |
/skill-creator | — | Sonnet | Guide for creating effective Claude Code skills |
Which review skill to use?
Short answer: if you don't know, use /review-full. It auto-detects scope and dispatches to the right workers.
flowchart TD
User([You]) -->|default| RF["/review-full<br/>dispatcher"]
User -.->|skip auto-detect| RC["/review-code-fix"]
User -.->|skip auto-detect| RU["/review-ux-fix"]
User -.->|skip auto-detect| RD["/review-docs"]
RF -->|any code in diff| RC
RF -->|frontend in diff| RU
RF -->|docs-only diff| RD
Ship["/ship Phase R"] --> RF
ShipD["/ship Phase D"] --> RD
classDef entry fill:#e0e7ff,stroke:#4f46e5,color:#1e1b4b
classDef worker fill:#fef3c7,stroke:#d97706,color:#451a03
classDef user fill:#d1fae5,stroke:#059669,color:#022c22
class RF entry
class RC,RU,RD worker
class User,Ship,ShipD user
Decision matrix:
| Situation | Use |
|---|
| 🟢 Default for any review | /review-full |
| Force code review only (skip UX even on FE diff) | /review-full --code-only |
| Force UX review only (skip code) | /review-full --ux-only |
| Backend-only PR, want to bypass scope detection | /review-code-fix directly |
| Pure CSS/spacing polish, no logic changes | /review-ux-fix directly |
| Verify docs only (after editing docs, or as audit) | /review-docs directly |
Rule of thumb: /review-full covers most cases. The direct workers (/review-code-fix, /review-ux-fix, /review-docs) are escape hatches for when you know exactly what you want.
How /ship works
flowchart TD
Start([/ship]) --> A
