tech debt architect

The problem

Legacy codebases often suffer from hidden coupling traps, security vulnerabilities, and performance bottlenecks that slow down feature delivery. Developers struggle to justify refactoring time to stakeholders who only care about business value and deadlines.

What it does

• Performs a multi-dimensional scan for code smells, architectural defects, security risks, and performance bottlenecks.
• Maps every identified debt to specific files, function names, and exact line ranges.
• Analyzes Git history to identify root causes like deadline rushes or multi-author collisions.
• Generates a prioritized P0 to P3 inventory with estimated remediation effort in person-days.
• Produces a dependency-aware refactoring roadmap with a phased execution plan.

Frameworks & tools

Works across any language. Utilizes Git, Glob, and Grep for deep repository analysis and history auditing.

Why this beats prompting it yourself

Generic prompts result in vague advice like "improve cohesion." This skill enforces a rigorous four-part architectural audit, requires concrete before/after code snippets for every recommendation, and uses Git forensics to prove why code is failing, making the business case for you.

Use cases

• Audit a new repository to assess maintainability and release risks.
• Create a phased refactoring roadmap that respects business-critical frozen zones.
• Identify high-risk security flaws like SQL injection or hardcoded secrets.
• Estimate the man-hours required to stabilize a fragile legacy module.

Known limitations

Requires access to source files for line-level accuracy. Git-based root cause analysis is unavailable for zip-file uploads or repos without history.