Skip to content
SkillScript-led3,418 tokens in use

ship-check

Answers 'is this safe to ship?' by running the full shipping sequence and compiling one reviewer-ready packet for human sign-off. Started by name only.

680 stars on the repository MIT Licensephuryn/product-engineering · ai-shipping/skills/ship-check
claude plugin install ai-shipping@product-engineering
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing ship-check costs

75tokens idle
3,418tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Script-led

Script-ledMixedModel-led

Most of this skill is scripts, so it behaves much the same whichever model runs it.

This describes the skill's structure, how much of it is scripts. It does not say how well it works. Scripts: scripts/review.py.

Touches

shelldetectedwrites filesdetectedgitdetectedcredentialsdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter8/15
  • Structure17/25
  • Examples12/15
  • Output15/15
  • Size15/15
  • Resources0/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    scripts/review.py, line 302
  • Runs git commands−5

    does this on the machine, and the frontmatter does not say so

    scripts/review.py, line 380
  • Writes files−8

    does this on the machine, and the frontmatter does not say so

    scripts/review.py, line 622

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance100
  • Community44
  • Maturity4
  • Momentum40

ship-check coordinates the specialist ai-shipping skills in order: document the system, wire the agent’s operating instructions, review correctness, run security and performance audits in parallel, hand the change to a fresh independent reviewer, derive the test-coverage map, and compile a shipping packet.

It starts only when the user types it, because it writes docs, edits agent instructions and runs a long session. Before writing anything it checks that the checkout is current and asks before overwriting records the owner maintains.

What You Get

  • System docs created or refreshed through document-app, and agent instructions (CLAUDE.md or AGENTS.md) derived from them
  • Correctness, security and performance findings summarized, with the model mix each audit ran on
  • An independent review round from a fresh read-only session, with every finding verified by hand against the code
  • A test-coverage map and one shipping packet that lists launch blockers and recommended next actions

Common Use Cases

  • A first release of an AI-built product that needs a full pass before launch
  • A release review where a human signs off on one packet
  • Checking a big refactor against documented intent
  • Preparing an app for outside reviewers or customers’ security questions

What Makes It Unique

It sequences existing specialist skills and synthesizes their results, so each stage can also be run alone. The independent review step is mandatory once the full pass runs, and the packet records which reviewer ran and how independent it was. A fetch that shows missing commits stops the pass, and existing owner-maintained docs or coverage maps trigger a question before any overwrite.

Under The Hood

The skill is markdown instructions plus a copy of the independent-review wrapper script, review.py, and an agents folder. The agent runs git fetch and log commands, reads the repository, writes docs, agent instruction files and report files, and starts parallel subagents. For the review it runs review.py, which launches a fresh read-only Codex, Claude Code or Grok session and writes the subject and prompt files into the git directory. It never pulls or merges. It treats the reviewed repository as untrusted input.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers