Skip to content
SkillMixed6,459 tokens in use

independent-review

A release gate built on a fresh, read-only reviewer that never saw the build: git-computed subjects, a five-part brief, mandatory triage and a clear stopping rule.

680 stars on the repository MIT Licensephuryn/product-engineering · ai-shipping/skills/independent-review
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 independent-review costs

39tokens idle
6,459tokens in use
12,239tokens, up to

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

Model dependence Mixed

Script-ledMixedModel-led

Scripts do part of the work and the model's judgement does the rest.

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
  • Structure19/25
  • Examples12/15
  • Output15/15
  • Size13/15
  • Resources11/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

    SKILL.md, line 48
  • 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

independent-review makes sure the session that wrote the code never clears it. A wrapper script starts a fresh Codex, headless Claude Code or Grok reviewer with read-only tools and no connectors or memory, feeds it a subject computed from git, and refuses a short round that only looks clean.

The rest of the skill is method: how to write a brief that does not steer the reviewer, how to triage each finding by what goes wrong for a person and how often, and when to stop.

What You Get

  • A wrapper command, review.py, that picks the reviewer, applies read-only flags and fails a round that is too short or lacks read evidence
  • A subject definition computed from git, with rules for splitting large ranges by commits or by surface
  • A five-part brief template and a triage procedure covering severity, frequency and the lines a finding must cross
  • A stopping rule: no introduced finding above Low and no High or Critical of any age
  • A reference on what each reviewer CLI still loads and how to run a round by hand

Common Use Cases

  • Reviewing a phase of AI-built work before pushing to a deploying branch
  • A whole-history review before a first release
  • Re-reviewing after each fix until a round is clean
  • Deciding which reviewer findings are real, rare or false

What Makes It Unique

It treats reviewer output and severity labels as claims to verify, and it builds the failure it found into the tooling: a round that exits 0 after one sentence is rejected. It requires a fresh session of the reviewer’s own, with fallback order across three model families, and records what could not be switched off. Its triage favors removing a rare case over adding machinery and records accepted Lows.

Under The Hood

The skill is a long markdown file, two reference files and one Python script. The script runs git commands to build the subject, writes the subject and prompt into the git directory, and launches a Codex, Claude Code or Grok command line in read-only mode with tools limited to reading and searching. It checks the reviewer’s event stream, reads binary location environment variables, and saves the report and events file where the user points. It makes no web calls of its own, and the reviewer’s web search is switched off. The agent also runs git status, log and diff itself.

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