AugmentClaude

Code Health

Scan your codebase for dead code, tech debt, and quality issues.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/code-health-davepoon/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Scans the codebase for dead code, tech debt, outdated dependencies, and code quality issues. Delegates to the Centinela (QA) agent.

What this skill does

Code Health

Runs a comprehensive code health scan using the Centinela (QA) agent.

When to Use This Skill

  • Periodic codebase hygiene check
  • Before a release to ensure no dead code or unresolved debt
  • After a large refactoring to verify cleanliness
  • When onboarding to understand current code quality

What This Skill Does

  1. Runs the SIGN IN checklist
  2. Scans for dead code (unused imports, variables, functions, commented-out blocks, unreachable code)
  3. Checks for outdated and vulnerable dependencies
  4. Detects code smells (long functions, deep nesting, duplication)
  5. Audits TODO/FIXME comments for issue references
  6. Runs the Scan Complete checklist (TIME OUT)
  7. Writes findings to docs/reviews/code-health-{date}.md
  8. Prepares findings handoff to Dev agent

How to Use

Basic Usage

/code-health

Example

User: /code-health

Output: A code health report at docs/reviews/code-health-2026-02-23.md with:

  • Dead code findings (verified, not false positives)
  • Dependency status and vulnerabilities
  • Code smell inventory
  • TODO/FIXME audit
  • Prioritized findings: Critical > Warning > Suggestion

Tips

  • Scans all source directories, not just src/ — includes tests/ and config files
  • Previous scan findings are compared to track recurring issues
  • Findings are verified to avoid false positives from dynamic imports or plugins

Related skills