production-readiness-review

production-readiness-review is a command for Claude Code from naimkatiman/continuous-improvement. It costs 65 tokens per session (849 once invoked), scanned A, original, MIT.

A reporting command that reviews whether an application is ready to ship by using separate checks for performance, security, user experience, tests, and simplicity.

In plain words
What is it for?
Use it to review the current branch changes, a path, or a pull request before release. It investigates issues such as slow code, security problems, missing tests, and interface defects.
Why use it?
It collects evidence-based findings into one severity-ranked list, so teams can see release risks without merging, fixing, or deploying anything automatically.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Good fit Use it to review the current branch changes, a path, or a pull request before release. It investigates issues such as slow code, security problems, missing tests, and interface defects.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/naimkatiman/continuous-improvement/production-readiness-review
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/naimkatiman/continuous-improvement

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for production-readiness-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/naimkatiman/continuous-improvement/production-readiness-review/github.svg)](https://agentmods.dev/commands/naimkatiman/continuous-improvement/production-readiness-review)
Your own site
<a href="https://agentmods.dev/commands/naimkatiman/continuous-improvement/production-readiness-review"><img src="https://agentmods.dev/badge/commands/naimkatiman/continuous-improvement/production-readiness-review/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for production-readiness-review

Your own site · 80×15
<a href="https://agentmods.dev/commands/naimkatiman/continuous-improvement/production-readiness-review"><img src="https://agentmods.dev/badge/commands/naimkatiman/continuous-improvement/production-readiness-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 849 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00065 $0.00849
Opus 5 $0.00032 $0.00425
Sonnet 5 $0.00013 $0.00170
Haiku 4.5 $0.00006 $0.00085

Measured 10d ago against content hash 073d21432f04, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

production-readiness-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/production-readiness-review.md · 55 lines

How it starts

The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/production-readiness-review

The review-side sibling of /ship. Fans a set of blind, specialized reviewers across distinct dimensions, then reconciles their findings into a single prioritized punch-list. It reports — it does not fix. Fixing a finding is a separate /ship run.

Pure routing over existing skills and agents. Adds no new code.

Usage

/production-readiness-review [scope]

scope defaults to the current branch diff against origin/main. Pass a path or PR number to narrow it.

Behavior

  1. Scope — establish ground truth: the diff under review and which changes are recent (git diff; reconcile fallback for branch/base state). Recent changes get extra scrutiny because they are the likeliest source of self-inflicted defects.
  2. Fan outsuperpowers:dispatching-parallel-agents launches five reviewers, each blind to the others. Every reviewer is instructed to ground each finding in real code, logs, or live queries, and never to assume or fabricate state:
    • Performance & bundle-size — hot paths, N+1 queries, unbounded work, regressions.
    • Security & data-access (security-auditor) — authn/authz, input handling, injection, secret exposure, unsafe data access.
    • UI/UX correctness — verified live with Playwright when the MCP is available, else static review of the changed surface.
    • Test coverage & flaky/stale mocks (test-engineer) — uncovered branches, stale mocks, timing-flaky tests.
    • Simplicity & over-engineering (simplicity-review) — code that could reuse an existing file, a stdlib or native feature, or fewer lines; reports trim opportunities via the reuse ladder and never flags input validation, data-loss handling, security, or accessibility.
  3. Reconcile — a final pass dedupes findings across reviewers, ranks each CRITICAL / HIGH / MEDIUM / LOW by severity and confidence, and explicitly flags any defect introduced by the changes under review.
  4. Present — emit the consolidated punch-list, severity-ranked, with file references. Stop.

Read the full file on GitHub · 55 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 55 lines · 65 tokens per session scan A 073d21432f04

Subscribe to this mod's changes

production-readiness-review is a command published in the GitHub repository naimkatiman/continuous-improvement (7 stars, last pushed 3d ago), licensed MIT. It adds 65 tokens to every session and 849 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.