cc-readiness-audit

Audit codebases for Claude Code deployment readiness across eight pillars.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/z23cc/cc-code --skill cc-readiness-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-readiness-audit
Source: https://github.com/z23cc/cc-code/tree/main/skills/cc-readiness-audit
Command: npx skills add https://github.com/z23cc/cc-code --skill cc-readiness-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

8-pillar project readiness assessment. Checks agent readiness (can Claude Code work effectively here?) and production readiness (is this deployable?). Fixes agent-readiness issues only; reports production issues without changing.

Core Features & Use Cases

  • Auto-detects agent readiness issues across Pillars 1-5 and applies auto-fixes where possible.
  • Reports production readiness (Pillars 6-8) without changing production code, guiding deployment decisions.
  • FLOWS INTO: cc-deploy to integrate with deployment workflows.

Quick Start

Run an automated readiness audit to verify agent readiness and production deployability.

Frequently Asked Questions about cc-readiness-audit

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

FAQPage Schema
How do I audit my project for Claude Code deployment readiness?

To audit project readiness, run an automated assessment that checks agent effectiveness and production deployability across 8 pillars, applying auto-fixes to agent gaps while reporting production issues without modifying code.

What is the difference between agent readiness and production readiness checks?

Agent readiness checks identify gaps preventing Claude Code from working effectively and apply auto-fixes, while production readiness checks evaluate build health, tests, observability, security, and CI/CD status, reporting issues without changing code.

Can I auto-fix build health and linting issues across different programming languages?

Yes, the readiness audit auto-detects agent readiness issues across multiple languages and environments, applying actionable auto-fixes to agent gaps while leaving production code unchanged.

Does the readiness audit modify my production codebase during security and CI/CD checks?

No, the audit assesses production readiness pillars including security and CI/CD without modifying production code, guiding deployment decisions through a structured report instead of applying changes.

How do I integrate readiness audit results into my deployment workflow?

The audit outputs a structured report that flows directly into cc-deploy workflows, allowing you to integrate readiness checks with deployment pipelines and guide production release decisions.

What specific areas does an 8-pillar project readiness assessment cover?

The 8-pillar assessment covers agent readiness, build health, tests, documentation, observability, security, and CI/CD readiness, providing a comprehensive evaluation of project deployability.