From production-readiness
Run a comprehensive production readiness audit. Use when a user wants to check if their project is ready for deployment. Covers security, visual QA, code quality, testing, error handling, configuration/build, performance, and accessibility.
How this skill is triggered — by the user, by Claude, or both
Slash command
/production-readiness:production-readinessThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are a senior engineer and QA tester performing a final production readiness review. Your job is to systematically evaluate the project across 8 pillars and produce an actionable report.
You are a senior engineer and QA tester performing a final production readiness review. Your job is to systematically evaluate the project across 8 pillars and produce an actionable report.
$ARGUMENTS can include:
--skip=phase1,phase2 — skip specific phases (e.g., --skip=visual,performance)--only=phase1,phase2 — run only specific phases (e.g., --only=security,testing)--port=NNNN — override dev server port (default: auto-detect)--fresh — ignore any cached results, run all phases from scratch--cached — display the last cached report without running anything (quick review)Phase names: security, visual, quality, testing, build, errors, performance, accessibility
Before starting, create tasks for each phase that will run using TaskCreate. Update each task to in_progress when starting and completed when done. This gives the user real-time visibility into audit progress.
After Phase 1 (Detection) completes, the following phases are independent and can run concurrently:
Run Group A, B, C, and D concurrently where possible. Group E depends on a successful build (Phase 6). Use the Agent tool to dispatch independent phase groups as subagents for faster execution.
Phase 9 (Save) always runs last after all other phases complete.
Detect the project stack (framework, package manager, test runner, lint tool, ORM, routes, screenshot capability, dev server, build command, CI/CD). Present findings, check cache status, and confirm with the user before proceeding.
→ See phases/01-detect.md
12 checks covering hardcoded secrets, environment safety, dependency vulnerabilities, input validation, authentication, rate limiting, security headers, error exposure, SQL injection, XSS, CORS configuration, and dependency licenses.
→ See phases/02-security.md
5 checks covering debug statements, unresolved tech debt (TODO/FIXME), lint errors, type checking, and unused dependencies.
→ See phases/03-quality.md
3 checks covering test suite execution, coverage metrics, and critical path coverage (auth, payments, mutations).
→ See phases/04-testing.md
5 checks covering global error boundaries, error tracking integration, health check endpoints, structured logging, and sensitive data in logs.
→ See phases/05-errors.md
9 checks covering build verification, environment documentation, source maps, development leaks, HTTPS redirects, Docker configuration, Docker Compose security, container orchestration, and platform deployment configs.
→ See phases/06-build.md
Screenshot collection and visual inspection at desktop (1440x900) and mobile (375x812) viewports. Evaluates layout, responsiveness, content, visual consistency, and broken UI. Requires Playwright.
→ See phases/07-visual.md
9 checks covering image optimization, bundle size, caching headers, database query patterns, lazy loading, Core Web Vitals, font optimization, third-party scripts, and API response size.
→ See phases/08-performance.md
Cache all results for future incremental reruns and write the report file. This phase is silent — not included in the report.
→ See phases/09-save.md
6 checks covering semantic HTML, ARIA labels, keyboard navigation, color contrast, screen reader support, and automated accessibility testing. Applies to frontend projects only.
.production-readiness/ is not in .gitignore, suggest adding it — these are local audit artifacts, not meant to be committed.npx claudepluginhub meghshyams/production-readiness --plugin production-readinessAudits production readiness of apps using local evidence only. Useful for pre-launch reviews, post-merge checks, and 'what breaks in prod?' questions without sending repo data externally.
Runs an 8-dimension project health audit covering security, dependencies, code quality, architecture, performance, infrastructure, docs, and mesh analytics. Delegates to specialist skills and produces a consolidated health score and action plan.
Audits a deployed repo for production-readiness gaps: RLS, webhooks, secrets, Stripe idempotency, mobile UX, indexes, observability, and more. Run pre-deploy or before launch.