From the author
Analyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.
Install
npx skills add oliver-kriska/claude-elixir-phoenix --skill techdebt -a claude-code
Installs to .claude/skills/techdebt/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 86
Security100
Provenance73
Maintenance100
Licence100
Adoption45
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- phx-techdebtoliver-kriska/claude-elixir-phoenixAnalyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.Engineering★ 569
- phx-reviewoliver-kriska/claude-elixir-phoenixReview changed Elixir/Phoenix code read-only. Check requirements, cite evidence, deduplicate findings, and return a severity-based verdict.Engineering★ 569
- phx-investigateoliver-kriska/claude-elixir-phoenixInvestigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence, and use optional native OpenCode subagents only when useful.Finance★ 569
- analyzeoliver-kriska/claude-elixir-phoenixAnalyze a legacy app in any language before rewriting it in Elixir: inventory, features as goals, why each mechanism exists, runtime topology, external contracts. Use to start or refresh a rewrite.Other★ 569
- phx-codex-loopoliver-kriska/claude-elixir-phoenixFix Elixir/Phoenix code until Codex CLI review comes back clean; Use when codex is installed and you want an external…Engineering★ 569
- brooks-debthyhmrright/brooks-lintTech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books. Triggers when: user asks about tech debt, refactoring priorities, what to clean up first, or asks "why is this so hard to change?", "what should we fix first?", or "how do I justify refactoring to management?". Do NOT trigger for: server health checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime — "health" in those contexts is infrastructure, not code quality. Also not for single-function refactoring questions.DevOps★ 1.5K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in