production-hardening
Production Hardening
Scan a codebase for resilience anti-patterns, generate a prioritized hardening playbook, and optionally implement the fixes.
Announce at start: "I'm using the production-hardening skill."
When to Use
- Before promoting a service to production
- When asked to "harden", "add resilience", or "make production-ready"
- When a post-incident review reveals missing retry/breaker/timeout patterns
- When migrating from prototype to production-grade code
When NOT to Use
- Security vulnerability scanning → use
security-auditor - Performance benchmarking / load testing
- Feature development unrelated to resilience
More from chandima/opencode-config
github-ops
|
2context7-docs
|
2mcporter
Direct MCP access via MCPorter. Use to discover MCP servers, list MCP tools, or call an MCP tool (e.g., chrome-devtools screenshot, firecrawl scrape) when no specific skill exists. Supports any configured MCP server.
1asu-discover
Semantic search across 760+ ASU GitHub repositories via RAG. Use for finding code patterns, integrations, SDKs, and ASU-specific conventions. Domains: PeopleSoft, EDNA, DPL, Terraform, EEL, Vault, CI/CD. Use BEFORE starting ASU integration tasks.
1skill-evals-run
Run the OpenCode skill-loading eval suite for this repo. Use when asked to run skill evals, skill-loading evals, or the skill-evals-run command.
1planning-doc
Create or update PLAN.md planning documents when users ask for a plan or planning. Use when asked to create a plan, planning document, or plan-based workflow.
1