Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.commanderplugin.com/llms.txt

Use this file to discover all available pages before exploring further.

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

Inside any Claude Code session:
/ccc:xray

​
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.
DimensionWeightWhat it checks
Security25%CVEs, exposed secrets, .env files tracked in git, lockfile integrity
Testing20%Test configuration, coverage, E2E frameworks, presence of test files
Maintainability20%Code complexity, linting config, formatting, duplication
Dependencies15%Outdated packages, known vulnerabilities
DevOps10%CI/CD presence, quality gates, deployment configuration
Documentation10%README.md, CLAUDE.md, inline docs, API documentation
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:
LevelNameTypical score rangeWhat it means
1Initial0–20No test infrastructure, no CI, likely no README
2Managed21–40Some structure in place but major gaps in at least 2 dimensions
3Defined41–60Consistent practices, CI present, basic test coverage
4Quantified61–80High coverage, security checks passing, full DevOps pipeline
5Optimizing81–100All dimensions healthy, docs current, zero known vulnerabilities

​
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
Project Health: 42/100 — Maturity: 2 (Managed)

Security      ████░░░░░░  38/100  ← No lockfile, 2 CVEs in deps
Testing       ██░░░░░░░░  20/100  ← No test files found
Maintainability ██████░░░░ 60/100  ← ESLint configured
Dependencies  ████████░░  78/100  ← 3 minor outdated packages
DevOps        ░░░░░░░░░░   0/100  ← No CI pipeline
Documentation ████░░░░░░  40/100  ← README present, no CLAUDE.md

Top recommendations:
  1. Add CI pipeline (impact: 85) → /senior-devops
  2. Create test files (impact: 90) → /tdd-workflow
  3. Create CLAUDE.md (impact: 80) → /project-kickoff

​
Running Makeover

After an XRay scan, run Makeover to apply the highest-impact fixes automatically: 
/ccc:makeover
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. 
Current Health: 42/100 (Maturity: 2 - Managed)

[1/5] No CLAUDE.md (impact: 80)
  -> Running /project-kickoff...
  -> Done. CLAUDE.md created.

[2/5] No test files (impact: 90)
  -> Running /tdd-workflow...
  -> Done. 12 test files created.

[3/5] No CI pipeline (impact: 85)
  -> Running /senior-devops...
  -> Done. .github/workflows/ci.yml created.

Updated Health: 71/100 (Maturity: 3 - Defined)
Improvement: +29 points

​
Makeover options

FlagWhat it does
--dry-runShow recommendations without applying any changes
--autoApply all recommendations without prompting
--max NLimit to N recommendations (default: 5)
--category CATFocus on one dimension only: security, testing, devops, quality, docs, or architecture
# Preview what Makeover would do without changing anything
/ccc:makeover --dry-run

# Fix only security findings
/ccc:makeover --category security

# Apply everything automatically, up to 10 recommendations
/ccc:makeover --auto --max 10
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.