agentleFS
OneDro1dOneDro1d/dark-factory/skills/production-readiness-reviewer/SKILL.md

production-readiness-reviewer

Skill4 starsChanged 2 months agoApache-2.0View on GitHub

Verify whether a service, feature, or contract is safe to deploy to production. Use when preparing for deployment, reviewing release candidates, or validating production configs. Triggers on "production ready", "deploy review", "release check", "pre-deploy", "go-live checklist", "launch readiness", "deployment review", "ready for prod".

  • Reads credentials

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify whether a service, feature, or smart contract is safe to deploy to production.

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Production Readiness Reviewer

Verify whether a service, feature, or smart contract is safe to deploy to production. Ensures all operational, reliability, and safety requirements are met before go-live.

Core Guardrails

:red_circle: If rollback is impossible, it's a red flag. :red_circle: If you can't observe it, you can't operate it.

When to Use

  • Preparing a service for first production deployment
  • Reviewing release candidates before deploy
  • Validating production configuration changes
  • Pre-launch checklist for new features
  • Smart contract deployment verification
  • Infrastructure changes going to production

Review Workflow

On EVERY invocation, execute these steps in order:

Step 1: Identify Deployable Unit

Determine what is being deployed:

TypeExamples
ServiceAPI, worker, microservice, lambda
FrontendWeb app, mobile app build
Smart ContractSolidity, Vyper, Rust/Anchor
InfrastructureTerraform, K8s manifests, cloud resources
ConfigurationFeature flags, env vars, secrets
DatabaseMigration, schema change

Document:

Deployable: [name]
Type: [service/frontend/contract/infra/config/database]
Version: [tag/commit/hash]
Target environment: [staging/production]

Step 2: Inspect Configuration

Review all configuration for production readiness:

# Find environment variables
grep -rn "process.env\|os.environ\|env::" --include="*.ts" --include="*.py" --include="*.go"

# Find config files
ls -la *.config.* .env* config/ 2>/dev/null

# Check for hardcoded values
grep -rn "localhost\|127.0.0.1\|:3000\|:8080" --include="*.ts" --include="*.yaml"

# Find feature flags
grep -rn "feature.*flag\|isEnabled\|FF_" --include="*.ts" --include="*.tsx"

Verify:

  • All env vars documented and have production values
  • No hardcoded development URLs/ports
  • Secrets come from vault/env, not code
  • Feature flags set correctly for production
  • Resource limits configured (memory, CPU, connections)

Step 3: Review Failure Modes

For each external dependency, answer:

DependencyWhat if unavailable?What if slow?What if returns bad data?
Database[behavior][behavior][behavior]
Cache[behavior][behavior][behavior]
External API[behavior][behavior][behavior]
Queue[behavior][behavior][behavior]

Step 4: Execute Checklist

See CHECKLIST.md for the complete production readiness checklist.

Output Format

A) Deployable Unit & Scope

Deployable: [name]
Type: [type]
Version: [version]
Changes since last deploy: [summary]
Blast radius: [what could break]

B) Blocking Issues

Issues that MUST be fixed before deployment:

### :red_circle: BLOCKER: [Title]

**Issue:** [Description]
**Risk:** [What could go wrong in production]
**Required fix:** [What must be done]

C) Non-Blocking Risks

Issues to be aware of, but not deployment blockers:

### :yellow_circle: RISK: [Title]

**Issue:** [Description]
**Likelihood:** [Low/Medium/High]
**Impact:** [Low/Medium/High]
**Mitigation:** [How to reduce risk]
**Follow-up:** [Post-deploy action item]

D) Rollback & Recovery Plan

Rollback method: [How to revert]
Rollback time estimate: [minutes]
Rollback complexity: [Simple/Complex/Impossible]
Data rollback needed: [Yes/No]
Rollback tested: [Yes/No]

Recovery steps:
1. [Step 1]
2. [Step 2]
3. ...

Escalation path:
- L1: [Who handles first]
- L2: [Escalate to]
- L3: [Final escalation]

E) Production Readiness Verdict

┌─────────────────────────────────────────────────────────────┐
│  VERDICT: [READY / NOT READY / READY WITH CONDITIONS]       │
├─────────────────────────────────────────────────────────────┤
│  Blocking issues: [count]                                    │
│  Non-blocking risks: [count]                                 │
│  Rollback feasible: [Yes/No]                                 │
│  Observability complete: [Yes/No]                            │
├─────────────────────────────────────────────────────────────┤
│  Recommendation: [Deploy / Fix blockers / Needs discussion]  │
└─────────────────────────────────────────────────────────────┘

Verdict definitions:

VerdictMeaning
:white_check_mark: READYSafe to deploy, no blocking issues
:yellow_circle: READY WITH CONDITIONSCan deploy if [conditions] are met
:red_circle: NOT READYBlocking issues must be resolved first

Quick Commands

# Check for debug/dev flags
grep -rn "DEBUG\|DEV_MODE\|development" --include="*.ts" --include="*.yaml"

# Find TODO/FIXME comments
grep -rn "TODO\|FIXME\|HACK\|XXX" --include="*.ts" --include="*.go"

# Check health endpoints
curl -s http://localhost:8080/health | jq

# Verify environment variables are set
env | grep -E "^(DB_|API_|AWS_|EXCHANGE_)" | wc -l

# Check for missing error handling
grep -rn "catch\s*{\s*}" --include="*.ts"  # Empty catch blocks

# Find hardcoded secrets
grep -rn "password.*=.*['\"]" --include="*.ts" --include="*.env*"

Resources

  • CHECKLIST.md - Complete production readiness checklist
  • RUNBOOK-TEMPLATE.md - Template for operational runbooks

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.