When is the best time to run the techdebt skill?

It is highly recommended to run this skill before major feature work to identify areas needing cleanup first, or whenever code quality concerns are raised.

What tools does this skill use to analyze Elixir code?

The skill leverages Credo for automated linting and static analysis, combined with targeted pattern matching for Ecto queries, changesets, and Phoenix controllers.

What are the 'Iron Laws' mentioned in the skill?

These are non-negotiable best practices including searching before refactoring, following the 'three strikes rule' for extraction, and ensuring test coverage exists before changes.

Does this skill automatically refactor my code?

No, it generates a prioritized report with specific remediation steps and effort estimates, allowing you to review and approve changes before implementation.

Elixir Technical Debt Analyzer

Name: Elixir Technical Debt Analyzer
Author: oliver-kriska

byoliver-kriska

•

개발자 도구

Analyzes Elixir and Phoenix codebases to identify technical debt, duplicate patterns, and high-impact refactoring opportunities.

The Elixir Technical Debt Analyzer is a specialized auditing skill designed to maintain high code quality in Phoenix and LiveView projects. It systematically scans for code duplication, anti-patterns, and architectural inconsistencies by integrating tools like Credo with custom Ecto and Controller pattern matching. By enforcing 'Iron Laws'—such as the Three Strikes Rule and composition-based abstractions—the skill provides developers with a prioritized roadmap for refactoring, ensuring that technical debt is addressed systematically before it impacts new feature velocity.

주요 기능

0162 GitHub stars

02Prioritized reporting with effort-to-fix estimations (Low/Medium/High)

03Detection of duplicate Ecto query patterns and redundant Repo calls

04Strict Credo integration for automated code quality and design consistency checks

05Identification of copy-pasted CRUD actions across Phoenix controllers

06Audit of duplicated changeset logic and validation patterns in domain contexts

사용 사례

01Conducting a comprehensive codebase audit before starting major feature development

02Automating the detection of code smells and anti-patterns during the review process

03Identifying and consolidating repeated business logic into shared query or domain modules

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add oliver-kriska/claude-elixir-phoenix techdebt

For use in Claude.ai and ChatGPT

Download Skill