Production Audit
- 1.4k installs
- 238k repo stars
- Updated August 5, 2026
- affaan-m/ecc
This is a copy of production-audit by affaan-m - installs and ranking accrue to the original listing.
production-audit is a Claude Code skill that runs a local production-readiness audit for developers who need to find deployment risks without sending repository data to external services.
About
production-audit is an ECC agent skill that performs a local production-readiness audit to surface issues that could break in production while keeping all repository data on the developer machine. The audit is designed for teams that want pre-deploy confidence without uploading code or configuration to third-party scanning services. Developers reach for production-audit when preparing a release, hardening an AI-assisted codebase, or validating that environment, dependency, and operational gaps are caught before traffic hits production. The skill originates from the Everything Claude Code collection and complements external CI checks with an offline-first review pass.
- Local-evidence production readiness audit that never leaves your machine
- Answers "is this production-ready", "what would break in prod", and "what did we miss"
- Works on deployed URLs, release branches, PRs, or current checkouts
- Maintainer-safe rewrite that removes third-party data sharing
- Distinguishes engineering triage from formal compliance audits
Production Audit by the numbers
- 1,408 all-time installs (skills.sh)
- +83 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/affaan-m/ecc --skill production-auditAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.4k |
|---|---|
| repo stars | ★ 238k |
| Last updated | August 5, 2026 |
| Repository | affaan-m/ecc ↗ |
How do you audit production readiness locally and privately?
Run a local production-readiness audit that surfaces what could break in prod without sending any repo data to external services.
Who is it for?
Developers preparing a release who need offline production-risk discovery on sensitive or air-gapped repositories.
Skip if: Teams that require managed cloud SAST platforms, continuous runtime monitoring, or penetration testing with external tooling.
When should I use this skill?
A release is approaching, production breakage risk is unknown, or repository data must stay local during the audit.
What you get
Production-readiness findings, deployment risk checklist, and local audit report with no external data transfer.
- Production-readiness findings
- Local audit report
- Pre-deploy risk checklist
Files
production-audit - 日本語翻訳進行中
このファイルの翻訳は実装中です。英語版は元のスキルファイルを参照してください。
詳細は：D:/tmp/everything-claude-code/skills/production-audit/SKILL.md
Related skills
Changelog AutomationAutomatically generate accurate, well-structured changelogs from commit history and Conventional Commits.11.2k38.5k
Msstore CliAutomate publishing, managing submissions, and handling CI/CD for Windows apps in the Microsoft Store.7k37.5k
Changelog GeneratorAutomatically turn git commit history into polished, customer-friendly release notes without manual rewriting.5.9k71.8k
Deploy ChecklistGenerate a complete pre-deployment verification checklist tailored to their service or release.4.6k23.3kOpensource PipelineSafely strip secrets, sanitize code, and generate required open-source files before releasing a private project publicly.4.3k238k
Community PublishInstantly share running services with public URLs, list projects on a discoverable dashboard, or open-source code to a community GitHub repository.3.9k21How it compares
Use production-audit when offline, local risk discovery matters more than integrating a cloud-based continuous security platform.
FAQ
Does production-audit send code to external services?
production-audit runs locally and is designed not to send repository data to external services. Findings are generated from an on-machine production-readiness review of the codebase and configuration.
When should production-audit be used?
production-audit should be used before deployment when teams need to surface production breakage risks, especially on sensitive repositories where external scanning or code upload is unacceptable.