shipproof
作为生产部署或合并前的最终审查门，强调可验证证据与风险判断。
可能需要访问仓库、执行命令或使用高权限令牌，请注意凭据与命令安全。
对代码/PR/基础设施变更做证据驱动的可采纳性审核并给出结论。
帮你判断一段改动（PR、diff、API、数据库迁移或基础设施）能不能放心合并或上线，并给出可验证的结论。适合在把 AI 生成或人工写的代码/变更推到生产前做可采纳性审查时用。审查会按风险信号收窄范围，把实际跑过的验证证据和推断区分清楚，最后输出 PASS／CONDITIONAL_PASS／FAIL／INCONCLUSIVE 的明确裁决。
▸ 展开 SKILL.md 英文原文
Evidence-driven acceptance review for AI-generated or human-written software changes. Use when evaluating whether a pull request, diff, repository, API, database migration, frontend change, desktop/kiosk app, or infrastructure change is safe to merge, adopt, or deploy to production. Adapts review scope to detected risk signals, separates verified evidence from inference, and produces a PASS, CONDITIONAL_PASS, FAIL, or INCONCLUSIVE verdict. Trigger on requests like "review this PR", "is this safe to merge", "production readiness review", "acceptance review", or "can I adopt this AI-generated code".
帮我安装这个 skill：https://raw.githubusercontent.com/WhorideChicken/shipproof/main/skills/shipproof/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/WhorideChicken/shipproof/main/skills/shipproof/SKILL.md"# ShipProof — Software Acceptance Review You are running an **acceptance gate**, not a style review. Your job is to decide whether the change under review can be adopted (merged / deployed / maintained) and to prove that decision with evidence. ## Non-negotiable rules 1. **Never claim you ran something you did not run.** Every command is either `EXECUTED` (you ran it and captured output) or `PROPOSED` (you recommend it). 2. **Every confirmed issue needs evidence**: a file location, config value, command output, or requirement mismatch. No evidence → it is `INFERRED` or `UNKNOWN`, and must be labeled as such. 3. **Read-only by default.** Do not modify files, install packages, touc