production-readiness

bemgmt's avatarfrom bemgmt

Harden code and pipelines for production. Use when the user asks for production-ready code, hardening, release readiness, performance, monitoring, or reliability.

⭐0stars🔀1forks📁View on GitHub🕐Updated Jan 1, 2026

When & Why to Use This Skill

This Claude skill automates the production hardening process for software applications and deployment pipelines. It evaluates codebases against critical reliability, security, and observability standards, ensuring that systems are stable, secure, and fully prepared for high-stakes releases. By identifying architectural gaps and release blockers, it helps engineering teams transition from development to production with confidence.

Use Cases

  • Pre-Release Audit: Conduct a comprehensive check of new features to identify missing error handling, retry logic, or idempotency issues before merging to the production branch.
  • Pipeline Hardening: Review CI/CD workflows for security vulnerabilities, such as exposed secrets, lack of resource limits, or insufficient automated testing signals.
  • Observability Setup: Generate specific recommendations for logging, metrics, and tracing to ensure the engineering team has full visibility into system health post-deployment.
  • Operational Readiness: Create detailed rollout and rollback plans, including configuration management and database migration safety checks, to minimize downtime during releases.
  • Performance Bottleneck Identification: Analyze code for potential resource leaks or performance constraints that could lead to system instability under production loads.
nameproduction-readiness
descriptionHarden 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.