$ loading_
Audit production readiness locally and uncover risks before or after release.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "production-audit" skill from askskill: 1. Download https://raw.githubusercontent.com/affaan-m/ECC/main/skills/production-audit/SKILL.md 2. Save it as ~/.claude/skills/production-audit/SKILL.md 3. Reload skills and tell me it's ready
Using the current project code and configuration, run a production readiness audit. Focus on environment variables, logging, error handling, monitoring, health checks, caching, database migrations, and rollback plans. Output findings grouped by high, medium, and low risk.
A launch audit report grouped by risk level with issue details, impact, and fixes.
Analyze this post-merge change set and identify what is most likely to break in production, especially configuration drift, dependency upgrades, side effects, concurrency, timeouts, and permission changes. List additional checks that should be added.
A production-focused change analysis listing likely failure points, triggers, and suggested validation steps.
Review this app from a “what breaks first in production” perspective. Consider startup flow, external dependencies, queue jobs, resource limits, and recovery behavior, then rank the most fragile modules with reasons.
A ranked list of fragile modules with failure reasons, impact analysis, and hardening recommendations.
Use this skill when the user asks whether an application is ready to ship, what could break in production, or what must be fixed before a launch. This is a maintainer-safe rewrite of the stale community production-audit idea: it keeps the useful production-readiness lens and removes unpinned external execution and third-party data sharing.
security-review first.Build the audit from local and user-authorized evidence. Do not run unpinned remote code, upload repository contents to third-party services, or call external scanners unless the user explicitly approves that specific tool and data flow.
Use this order:
Start with cheap, local signals:
git status --short --branch
git log --oneline --decorate -20
git diff --stat origin/main...HEAD
Then inspect the project-specific surface:
If a deployed URL is in scope, use browser or HTTP checks only against that URL and avoid credentialed actions unless the user supplies a safe test account.
…
Design composable Top-K recommendation, ranking, and feed pipelines for user-context decisions.
Build testable Swift code with protocol-based dependency injection and focused mocks.
Apply Laravel security best practices for auth, vulnerabilities, APIs, and deployment.
Provides systematic verification for Claude Code sessions to improve correctness and quality.
Coordinate multi-agent teamwork with ownership, Kanban flow, merge gates, and handoffs.
Review Solidity AMM, liquidity pool, and swap flow security risks.
Run a structured code review before commit or release on local or PR branches.
Check whether an app is production-ready across security, reliability, and performance.
Assess app production readiness with 52 checks for security, reliability, and performance.
Audit Convex performance issues across reads, subscriptions, writes, and function limits.
Audit ECC Tools cost anomalies and trace misuse, leakage, and duplicate jobs.
Audit liability clauses against company standards with evidence-based verdicts or abstention.