production-readiness
Harden code and pipelines for production. Use when the user asks for production-ready code, hardening, release readiness, performance, monitoring, or reliability.
When & Why to Use This Skill
This Claude skill automates the production readiness review process by hardening code and CI/CD pipelines. It evaluates critical factors such as reliability, observability, security, and performance to ensure software is stable, secure, and ready for release. By identifying gaps in error handling, monitoring, and resource limits, it helps developers transition from development to production with confidence while minimizing deployment risks.
Use Cases
- Pre-release Audit: Reviewing a new feature branch to ensure it meets reliability standards like retries and idempotency before merging to the main branch.
- Security Hardening: Identifying exposed secrets, PII handling issues, or dependency risks within the codebase and deployment scripts to prevent vulnerabilities.
- Observability Integration: Verifying that necessary logging, metrics, and tracing are implemented to allow for effective production monitoring and rapid incident response.
- Performance Optimization: Checking for potential bottlenecks, resource limits, and profiling needs to ensure the application can handle production traffic loads.
- Operational Readiness: Validating configuration management, migration strategies, and rollout/rollback plans to ensure smooth deployment cycles.
| name | production-readiness |
|---|---|
| description | Harden code and pipelines for production. Use when the user asks for production-ready code, hardening, release readiness, performance, monitoring, or reliability. |
Production Readiness
Overview
Apply production hardening checks and identify missing pieces before release.
Checklist
- Reliability: error handling, retries, idempotency, timeouts.
- Observability: logging, metrics, tracing, alerts.
- Security: secrets handling, PII, access control, dependency risks.
- Performance: profiling, resource limits, bottlenecks.
- Operations: configs, migrations, rollout and rollback.
- Testing: unit, integration, smoke coverage, and CI signals.
Output
- List concrete gaps with recommended fixes.
- Suggest minimal test plan to prove readiness.
- Call out any release blockers.
- Be explicit about what was not verified.
Acceptance Criteria
- Gaps are mapped to concrete fixes and owners or next steps.
- Readiness verdict is stated with evidence vs assumptions.