Audit Refactor Opportunities

Identify code smells and refactoring opportunities.

When to Use

• •Tech debt assessment
• •Planning refactoring sprints
• •Understanding codebase health

Approach

Step 1: Project Invariants (Required)

Before auditing, check docs/knowledge-base/ for code style constraints:

• •AGENTS.md — established patterns
• •RULES-*.md — code organization rules
• •Flag any violation of documented patterns as higher priority.

Step 2: Focus Areas

• •Code Smells: Duplication, long functions, deep nesting
• •Pattern Violations: Inconsistent patterns across similar code
• •Naming: Unclear or inconsistent naming
• •Complexity: Overly complex logic that could be simplified
• •Dead Code: Unused exports, commented code

Checklist

• • Duplicated logic that could be shared
• • Functions >50 lines that could be split
• • Deeply nested conditionals (>3 levels)
• • Inconsistent patterns for similar operations
• • Unclear variable/function names
• • Dead or commented-out code

Output

Prioritized list of refactoring opportunities with effort estimates (Low/Medium/High).

Constraints

• •Identify only — do NOT fix
• •Fixes go through /refactor or /quick-fix