XRay is a project health audit that produces a score from 0 to 100 and a maturity level from 1 to 5. Makeover is the follow-up command that takes XRay’s output and automatically applies the top-priority fixes using a Claude agent swarm. Together, they give you a clear picture of where a codebase stands and a fast path to improving it.
Running XRay
Slash command
Headless dispatch
Main menu
Inside any Claude Code session: From the terminal, without an interactive session: Run ccc, select Research & analyze (d) from the main menu, then choose Code audit / review.
The 6 audit dimensions
XRay scans the project and scores each of the following dimensions independently. The weighted scores are summed to produce the overall health score.
Security carries the highest weight at 25% because findings in this dimension — exposed credentials, known CVEs, untracked lockfiles — carry the highest risk in production. A project with perfect testing and documentation but failing security checks will score below 75/100 overall.
Maturity levels
Every XRay report assigns a maturity level in addition to the numeric score:
XRay output
The XRay report includes:
- Overall health score and maturity level
- A score bar for each dimension
- Prioritized recommendations with the relevant skill to run for each finding
- Quick-fix commands for immediate wins
Running Makeover
After an XRay scan, run Makeover to apply the highest-impact fixes automatically:
Makeover re-runs XRay to get the current state, then presents the top 5 recommendations sorted by impact score. For each recommendation, it offers three choices: apply it automatically using the recommended skill, skip to the next one, or stop the makeover.
Makeover options
Run XRay before starting any new project or onboarding onto an existing codebase. The baseline score tells you exactly which dimensions need attention before you add features, and it gives you a concrete target to hit before calling a codebase production-ready.
Makeover applies changes directly to your working directory. Commit or stash any in-progress work before running Makeover with --auto, so you can review or revert the changes as a clean diff.