ship-check
Skill1 starsChanged 5 months agoMITView on GitHub
Pre-ship gate before commit or push — runs lint, typecheck, tests, build, secret scan, and git diff review, then outputs a READY/BLOCKED verdict with a proposed commit message. Never commits without explicit user confirmation. Triggers on "ship check", "ready to commit", "pre-push check", "commit and push", "ship this", "can I push".
- Reads credentials
19 other projects use a version of this.
Adopted by
Most recently taken up by
- Archive228/claude-fable-rea-blatheir own version, first seen Nov 15, 2026
- nadavnaveh/skillstheir own version, first seen Nov 8, 2026
- kitloomlk-stack/nextjs-supabase-kittheir own version, first seen Oct 15, 2026
- textura-agency/next16-claude-startertheir own version, first seen Oct 14, 2026
- joetawil7/first-passtheir own version, first seen Oct 14, 2026
- fightingforsidewalk/vault-relaytheir own version, first seen Oct 13, 2026
Used with
Projects with it also use review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- facontidavide/PlotJuggler★ 6.3ksame name
- textura-agency/next16-claude-starter★ 141same name
- joetawil7/first-pass★ 128same name
- Archive228/claude-fable-rea-bla★ 18same name
- mohankrishnaalavala/context-router★ 11same name
- Aximande/agent-skills★ 4same name
- koach08/claude-code-skills★ 4same name
- AhmedMerza/agent-skills★ 2same name
- AhmedMerza/claude-skills★ 2same name
- fightingforsidewalk/vault-relay★ 2same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- architect-enterprise-aiSkill
- author-agent-skillsSkill
- build-agent-harnessesSkill
- build-aiewf-2024-ragSkill
- build-generative-mediaSkill
- build-multimodal-productsSkill
- build-rag-search-stacksSkill
- build-robotics-aiSkill
- build-with-deepmindSkill
- build-with-microsoft-aiSkill
- build-with-openaiSkill
- deploy-public-sector-aiSkill
- design-agent-skillsSkill
- evaluate-with-braintrustSkill
- lead-ai-engineering-teamsSkill
- lead-ai-transformationSkill
- learn-summit-2023-remoteSkill
- learn-summit-2023-talksSkill
- navigate-aie-europe-2026Skill
- navigate-aiewf-2024-keynotesSkill
- observe-ai-productionSkill
- operate-agent-memorySkill
- operate-legal-ai-agentsSkill
- operate-openclaw-agentsSkill
- optimize-llm-inferenceSkill
- plan-sovereign-aiSkill
- price-ai-productsSkill
- run-aiewf-2024-evalsSkill
- run-llm-evalsSkill
- run-summit-2023-workshopsSkill
- secure-ai-agentsSkill
- ship-ai-as-pmSkill
- ship-aiewf-2024-agentsSkill
- train-llms-locallySkill
- architecture-reviewSkill
- chat-failure-auditSkill
- create-a-skillSkill
- cross-model-reviewSkill
- cto-weekly-reviewSkill
- friction-auditSkill
- ig-carouselSkill
- pdf-reportSkill
- raise-prSkill
- reel-editSkill
- research-reportSkill
- spec-grounded-designSkill
- state-lifetime-decisionSkill
- ste100Skill
- scroll-engineeringSkill
- ui-uxSkill
- verify-like-a-userSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 7 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Run automated checks + human-readable diff review before any commit or push.
- Very specific: line 22
Scripts: read scripts/ship-check.sh before running.
- Distinctive: line 44
Run in parallel where possible:
- Very specific: line 62
If scripts/ship-check.sh is not in cwd, locate it from the skill folder or run equivalent checks manually per checklist.md.
- Distinctive: line 71
Read checklist.md. Manually inspect the diff for:
- Distinctive: line 92
Use conventional commits unless the repo uses something else.
- Distinctive: line 121
Ask: "Commit?" — only proceed on yes
- Distinctive: line 122
Ask: "Push?" — only if user wants push, and only after successful commit
- Distinctive: line 124
If BLOCKED, list fixes needed.
“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Ship Check — Pre-Ship Gate
Run automated checks + human-readable diff review before any commit or push. Never commit or push unless the user explicitly confirms after seeing the report.
Works with any coding agent with shell access.
Supporting files:
- checklist.md — manual gate items
- report-template.md — output format
- scripts/ship-check.sh — automated checks
Scripts: read scripts/ship-check.sh before running. It executes project lint/test/build
commands — review what it will run in this repo. Double-check every time.
Output: {SKILL_OUTPUT_DIR}/ship-check/ — see ../OUTPUT.md
Step 0 — Scope
Infer or ask:
| Setting | Default |
| Skip build | no — unless user says "skip build" |
| Skip tests | no — unless user says "skip tests" or "quick check" |
| Commit after | only if user confirms after report |
| Push after | only if user explicitly asks after commit succeeds |
Step 1 — Collect State
Run in parallel where possible:
git status
git diff
git diff --cached
git branch --show-current
git log -3 --onelineThen run automated checks:
bash scripts/ship-check.sh
# Optional: SHIP_CHECK_STRICT=1 bash scripts/ship-check.sh
# Flags: --skip-build --skip-testsIf scripts/ship-check.sh is not in cwd, locate it from the skill folder or run
equivalent checks manually per checklist.md.
Review script output: lines prefixed PASS|, WARN|, FAIL|, DIFF_STAT|, SUMMARY|.
Step 2 — Diff Review
Read checklist.md. Manually inspect the diff for:
- Scope creep unrelated to the task
- Secrets, tokens,
.envfiles - Debug logging left behind
- Breaking changes without migration notes
Assign verdict:
| Verdict | When | |
| BLOCKED | Any `FAIL | ` from script, secrets in diff, or broken build/tests |
| READY WITH WARNINGS | Warnings only, or user waived a check | |
| READY | All checks pass, diff looks intentional |
Step 3 — Draft Commit Message
Analyze the full diff. Match the repo's existing commit style (git log -5).
Use conventional commits unless the repo uses something else. Focus on why, not just what.
Step 4 — Write Report
Fill report-template.md.
Path: {output_dir}/ship-check-YYYY-MM-DD-HHMM.md
Update {output_dir}/index.md:
# Ship Checks
| When | Branch | Verdict | Report |
|------|--------|---------|--------|Append newest first.
Step 5 — Present to User
- Verdict in one line (READY / READY WITH WARNINGS / BLOCKED)
- Blockers and warnings (if any)
- Proposed commit message in a copy-paste block
- Path to saved report
- Ask: "Commit?" — only proceed on yes
- Ask: "Push?" — only if user wants push, and only after successful commit
If BLOCKED, list fixes needed. Do not commit.
Edge Cases
- Clean working tree — report READY with note "nothing to commit"
- Staged + unstaged mix — show both diffs; ask what to include
- Monorepo — run checks from correct package directory or root per project convention
- No package.json — rely on checklist + git review; skip Node checks
- User says "commit anyway" on BLOCKED — warn once, then follow explicit override
- Pre-commit hook fails — fix issue, re-run ship-check, new report (never amend unless user rules allow)
Invocation Examples
ship check
ready to commit?
pre-push check
commit and push ← runs gate first; commit/push only after confirmation
quick ship check — skip tests
ship this branchDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

