Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →oliver-kriska/phx-techdebt
Analyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues.
Passed 14 of 20 test cases with the skill, and 8 of 20 without it.
and 6 more in the full report
7 fixed9 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are compiling a technical debt audit report for our Phoenix project. List the exact four fields required for reporting each identified code duplication.
| Checked | Without skill | With skill |
|---|---|---|
| Includes Location as a required reporting field. | Passed | Passed |
| Includes Extraction as a required reporting field. | Missed | Passed |
| Includes Effort as a required reporting field. | Missed | Passed |
The instructions your model reads when the skill loads.
Find and eliminate duplicate code patterns, anti-patterns, and refactoring opportunities in Elixir/Phoenix projects.
Run mix credo --strict.
Focus on:
Use Grep to search for repeated Repo calls (Repo.get!, Repo.get, Repo.one) in lib/**/*.ex.
Use Grep to find duplicate query patterns (from.*in.*where) in lib/**/*.ex.
Use Grep with output_mode: "count" to count def changeset occurrences in lib/**/*.ex.
Use Grep to find repeated validations (validate_required, validate_format) in lib/**/*.ex.
Use Grep to find similar action patterns (def create, def update, def delete) in lib/*_web/**/*.ex.
| Pattern | Symptom | Solution |
test cases passed, vs 8 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.