phx:techdebt

To detect technical debt in an Elixir Phoenix project, this Skill analyzes your codebase for duplicate Ecto queries, validation logic, and controller actions using command-line tools and grep, providing a structured report of locations and patterns.

The best way to find refactoring opportunities in Elixir code is by scanning for repeated patterns and consistency issues using Credo, which identifies design flaws and suggests specific extractions to improve maintainability.

No external dependencies are required to run this technical debt analysis, as it leverages built-in command-line tools and grep to scan your Elixir and Phoenix codebase directly without needing additional installed packages.

You get a prioritized roadmap for fixing duplicated Ecto queries by running this analysis, which provides a structured report detailing identified patterns, suggested extractions, and the estimated effort required for remediation.

You should scan your Phoenix codebase for technical debt when the project feels sluggish or difficult to modify, allowing you to get a clear roadmap of where to focus refactoring efforts for maximum impact.