Clean Code

Audit code against the bbv Clean Code Cheat Sheet (Urs Enzler, V2.2) — Clean Code principles plus Clean ATDD/TDD practices — then deliver a findings report and a phased, task-level implementation plan ordered by priority.

When to Use

This skill is user-invoked only. Run it only when the user explicitly:

• invokes /clean-code, or
• asks for a "clean code audit", "clean code review", "check this against clean code", "how clean is this code", "clean code report", or "clean code plan".

Do not auto-trigger on general coding, bug-fixing, feature work, performance tuning, or ordinary PR review — those belong to code-review, code-optimizer, or test-coverage. If a request is ambiguous (plain "review this code"), assume the user wants code-review and ask before running this audit.

What It Produces

CLEAN_CODE_AUDIT.md (always), written to the repo root, containing:

1. Findings grouped by cheat-sheet category, each citing file:line and a principle/smell label.
2. A phased implementation plan split by priority — Phase 1 (Critical) → Phase 2 (Major) → Phase 3 (Minor) — where every task has an ID, a target file:line, the principle it fixes, an effort estimate, and an acceptance check.