production-audit

Audit a codebase across six production readiness dimensions and generate PRODUCTION-AUDIT.md.

2|1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/costa-marcello/skillkit --skill production-audit-costa-marcello
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: production-audit
Source: https://github.com/costa-marcello/skillkit/tree/main/skills/production-audit
Command: npx skills add https://github.com/costa-marcello/skillkit --skill production-audit-costa-marcello

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audits a codebase for production readiness across six dimensions: API completeness, frontend-backend sync, security, scalability, infrastructure, and dead code/architecture.

Core Features & Use Cases

  • Structured, multi-dimension audits that produce a read-only assessment with evidence.
  • On-demand, isolated sub-agent execution that culminates in a consolidated PRODUCTION-AUDIT.md.
  • Flexible scope control via ARGUMENTS to focus on a subset of dimensions or to ignore non-critical areas.

Quick Start

Run a production audit on the target repository to generate PRODUCTION-AUDIT.md with prioritized blockers.

Frequently Asked Questions about production-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What does a production readiness audit cover for a codebase?▼

A production readiness audit covers six dimensions: API completeness, frontend-backend sync, security, scalability, infrastructure, and dead code. It produces a read-only assessment with evidence to support launch decisions.

Can I scope a production audit to check only security and scalability without reviewing the entire codebase?▼

Yes, you can scope the production audit to specific dimensions using ARGUMENTS. This allows you to focus the security and scalability checks on a subset of areas or ignore non-critical sections of your codebase.

How do I check frontend-backend sync and dead code during a pre-deployment review?▼

You can check frontend-backend sync and dead code by running a production audit. It assesses architecture and integration alignment, outputting a consolidated PRODUCTION-AUDIT.md file with evidence for pre-deployment reviews.

What is the output format of a multi-dimension codebase production audit?▼

The output format of a codebase production audit is a consolidated PRODUCTION-AUDIT.md file. It contains the structured, read-only assessment with evidence gathered from isolated sub-agent execution across all evaluated dimensions.

When should I not use an automated production audit for launch decisions?▼

You should not rely solely on an automated production audit when you need runtime performance testing or live infrastructure monitoring. The audit evaluates static codebase architecture and configuration, producing a read-only assessment rather than live execution metrics.