code-health
The code-health skill runs a comprehensive scan of a codebase to identify dead code, outdated dependencies, code smells, and unresolved technical debt, then generates a detailed report with prioritized findings. Use it before releases, after major refactoring, during periodic maintenance checks, or when assessing code quality for onboarding purposes.
git clone --depth 1 https://github.com/davepoon/buildwithclaude /tmp/code-health && cp -r /tmp/code-health/plugins/agent-triforce/skills/code-health ~/.claude/skills/code-healthSKILL.md
# 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 pluginsCreates a complete product feature specification with acceptance criteria, scope, dependencies, and risks. Delegates to the Prometeo (PM) agent.
Implements a feature from its specification. Reads the spec, designs architecture, writes code and tests. Delegates to the Forja (Dev) agent.
Pre-release verification checklist. Validates features, tests, docs, security, and quality gates before shipping. Delegates to the Centinela (QA) agent.
Addresses and fixes findings from a QA code review. Reads the review report, fixes critical and warning issues, and prepares for re-verification. Delegates to the Forja (Dev) agent.
Deep security audit covering OWASP Top 10, authentication, authorization, data protection, dependency vulnerabilities, and secrets scanning. Delegates to the Centinela (QA) agent.
Initialize uc-taskmanager for the current project. Creates works/ directory and configures Bash permissions in .claude/settings.local.json. Use when the user says "uctm init", "initialize uctm", "uctm 초기화", or "초기화".
Triggers the WORK-PIPELINE when a user request starts with a [] tag (e.g., [new-feature], [bugfix], [WORK start]). Use this skill whenever you detect a [] tag at the beginning of a user message.