ship-check

Featured

Is this safe to ship? Documents the app, wires the agent's context, runs the correctness, security and performance reviews and an independent unsteered pass, maps test coverage, and compiles one reviewer-ready shipping packet. Started by name only: /ai-shipping:ship-check in Claude Code, $ai-shipping:ship-check in Codex.

AI & Automation 633 stars 85 forks Updated today MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Ship check -- Is This Safe to Ship? **Run the full shipping sequence and compile a packet for human sign-off.** The question is "is it safe to ship?" The shipping packet brings the results together into one reviewer-ready artifact. **Run this pass only when the user starts it.** It writes docs, edits agent instructions and spends a long session. It coordinates the specialist skills rather than replacing them; each also runs on its own when asked. ## Invocation ``` /ai-shipping:ship-check Claude Code, plugin installed /ai-shipping:ship-check the payments service $ai-shipping:ship-check supabase/functions Codex, plugin installed /ship-check · $ship-check the skill folder copied into a repository ``` ## The shipping sequence **Run the steps in order on the requested scope.** Accept a path or area, or use the whole repository if none was given. Each audit needs documented intent to compare against the code, so each step builds on the last. ### Before step 1: say what this pass would overwrite **First, fetch, and bring the checkout up to date before anything is written**. Every step documents or audits this checkout; an older one is code that is no longer the product. Run `git fetch`; a failed fetch stops the pass. Then list what the remote has that the checkout lacks: - With an upstream: `git log --oneline 'HEAD..@{u}'`. - Without an upstream: `git log --oneline HEAD..origin/HEAD`. If that ref is missing, `git remot...

Details

Author
phuryn
Repository
phuryn/product-engineering
Created
2 weeks ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

ship-check

Pre-ship checklist for any script, tool, or repo the agent writes or packages, run before code leaves the session and before the handback is written: path traversal, command injection, secrets and names, placeholders, .gitignore, license, atomic writes, and proof that every guard has been seen to fail. Use it whenever a session is about to hand back a change that ships executable code, and name the sections that did not apply.

0 Updated 1 months ago
fightingforsidewalk
AI & Automation Listed

ship-checklist

When the user wants to know what is left before a repo is shippable, or wants the ship sequence. Triggers: 'is this ready to ship', 'ship checklist', 'what is missing before release'. Audits the repo against a shippable bar and sequences the other ship-skills.

1 Updated 2 months ago
royalpinto007
Code & Development Listed

pm-ai-ship-audit

AI 生成代码的上线前审计技能(vibe-coded app 交付审计)。两个方法 + 五条流程: 「文档基线」(架构、用户与权限流、权限矩阵、变量与密钥、测试覆盖地图,外加邮件/定时任务/SEO/内嵌 Agent 四个条件文档)、 「意图 vs 实现」(找文档写了但代码没做到的差距——通用扫描器发现不了的那一类 bug); 流程含反向补文档、推导测试覆盖、静态安全审计、静态性能审计(专抓 N+1 与请求瀑布)、上线检查总装。 能力:(1) 给 AI 写出来的代码补齐可评审的文档基线 (2) 交叉核对文档意图与代码实现的差距 (3) 出带证据行(file:line + 原文片段)且经过自我反驳的审计报告。 触发词:「上线前检查」「AI 代码审计」「vibe coding 检查」「代码和文档对不上」「权限有没有漏」 「安全审计」「性能审计」「N+1」「请求瀑布」「补系统文档」「测试覆盖地图」「ship check」, 或者用户说「这个项目是 AI 写的,能上线吗」时。 不适用:常规代码评审 → /code-review(Claude Code 内置,Codex/Cursor 无此技能);架构与详细设计文档 → hld-design / lld-design; 测试用例设计 → pm-test-cases;系统性排障 → systematic-debugging。 参考文档为英文原文,产出语言跟随用户提问语言。

1 Updated 2 months ago
iDWong