agent-diff-ship-check
Skill1 starsChanged 3 months agoMITView on GitHub
Pre-merge ship check for AI/agent-generated diffs. Use on uncommitted changes or PRs written mostly by agents, or Chinese "Agent 改动能不能合", "AI PR 检查", "上线前检查". Focus on ship risk, not style nits.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- customer-bug-to-failing-testSkill
- dead-code-safe-deleteSkill
- env-drift-checkSkill
- feature-flag-lifecycleSkill
- flake-vs-bug-triageSkill
- minimal-repro-packSkill
- secret-redact-before-aiSkill
- using-ship-guard-skillsSkill
The file
Files
Agent Diff Ship Check
Overview
AI diffs fail differently: missing tests, silent behavior change, secrets, incomplete migrations, debug leftovers. Produce a go / no-go with blockers.
Checklist axes
- Intent — what was supposed to change vs what did
- Correctness risk — edge cases, nulls, authz
- Tests — added/updated? gaps?
- Migrations / flags — safe rollout?
- Secrets & debug — keys,
console.log, TODOs that ship - Scope creep — unrelated files
- Rollback — can we revert cleanly?
Steps
- Collect diff (
git status/git diff/ PR). - Summarize intent in one sentence (ask user if unclear).
- Walk checklist; record blockers vs warnings.
- Required commands to run before merge (test, lint, migrate dry-run).
- Verdict: ship | ship-with-followups | block.
Exit criteria
- Diff scope summarized
- Checklist completed
- Blockers explicit
- Verdict stated
Anti-patterns
- Style-only review
- “LGTM” without tests when behavior changed
Output template
## Agent diff ship-check
### Intent
...
### Findings
| severity | item | why |
|----------|------|-----|
### Commands before merge
- [ ] ...
### Verdict
- **block** | **ship-with-followups** | **ship**Does 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.

