# Validate Production Readiness

Production releases can fail when quality, security, documentation, and rollback checks happen late. This skill guides Claude, Codex, and Claude Code through a structured pre-deployment audit.

## Install

```bash
npx skillstore add dnyoussef/production-readiness
```

## Metadata

- Status: approved
- Slug: dnyoussef-production-readiness
- Version: 1.0.0
- Author version: 1.0.0
- Skillstore revision: r1
- Version status: valid
- Tree hash: 19180ec78fdc18e6713adf27f74c119c8a7f58fce63c8d5d5671b4b1c50ccfa0
- Author: DNYoussef
- GitHub username: DNYoussef
- License: MIT
- Repository: https://github.com/DNYoussef/ai-chrome-extension/tree/main/.claude/skills/production-readiness
- Ref: c579efd02184f1128d6741d16e6c8d951d7d4208
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem, env\_access
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/dnyoussef-production-readiness
- Manifest: https://skillstore.pages.dev/api/skills/dnyoussef-production-readiness/manifest

## Capabilities

- Runs a staged readiness workflow across tests, quality, coverage, security, performance, documentation, dependencies, and monitoring.
- Generates a deployment checklist with gate status, sign-off items, deployment steps, and rollback steps.
- Checks for required release documents, including README, deployment guidance, and rollback plans.
- Uses local project reports to calculate pass or fail status for deployment gates.
- Scans source files for common secret keywords and logging framework indicators.
- Supports production and staging modes with an option to skip performance checks.

## Use Cases

- Release Manager Gate Review: Validate that release gates pass before approving a production deployment.
- Developer Preflight Check: Run a local readiness review before requesting deployment approval.
- DevOps Rollout Preparation: Create a checklist that covers deployment steps, monitoring, sign-offs, and rollback tasks.

## Prompt Templates

### Basic Readiness Review

```
Use the production-readiness skill to review this project for production deployment. Focus on tests, documentation, security, and clear blockers.
```

### Staging Deployment Check

```
Assess production readiness for the staging environment. Identify warnings separately from blockers and create a short action list.
```

### Production Gate Audit

```
Run a strict production readiness review. Include quality gates, security concerns, performance status, required documents, and deployment sign-offs.
```

### Release Remediation Plan

```
Review the failed readiness results and produce a prioritized remediation plan with owners, severity, verification steps, and rollback considerations.
```

## Limitations

- Requires local shell access and expected command-line tools to be available.
- The workflow assumes JavaScript or TypeScript projects for several source scans.
- Performance checks depend on available benchmark data and may not represent real production traffic.
- Secret scanning is keyword-based and can miss encoded, renamed, or externally stored secrets.

## Best Practices

- Run the skill from the project root so file and documentation checks use the correct scope.
- Review command output before sharing reports because scans may reveal sensitive file names or values.
- Keep release thresholds, service-level objectives, and rollback ownership documented before the final audit.

## Anti Patterns

- Do not treat a generated checklist as approval without human sign-off.
- Do not run secret scans on directories that include unrelated private repositories.
- Do not skip performance checks for production unless a release owner accepts the risk.

## Security Audit

- Audited at: 2026-07-05T12:21:46.505\+00:00
- Summary: The audit found many false positives caused by Markdown fences, inline command references, and documented shell reporting logic. One static finding is confirmed because the secret keyword scan can print sensitive source lines, and one semantic finding covers unpinned npx-based CLI execution.

## Stats

- Views: 203
- Downloads: 9
- Favorites: 0
- Popularity score: 0