Technical Debt Patterns

npx skills add majiayu000/claude-skill-registry --skill technical-debt-patterns --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

# Technical Debt Patterns Expert patterns for detecting, categorizing, and prioritizing technical debt in Rails applications. ## Decision Tree: Debt Category Identification ``` What type of issue is this? │ ├─ Code structure problem? │ ├─ Method too long (>20 lines) → Code Smell: Long Method │ ├─ Class too large (>150 lines) → Code Smell: Large Class │ ├─ Excessive parameter passing → Code Smell: Data Clump │ └─ Method uses another object's data → Code Smell: Feature Envy │ ├─ Complexity issue? │ ├─ Flog score >60 → Complexity: High │ ├─ Cyclomatic complexity >10 → Complexity: High │ ├─ Deep nesting (>3 levels) → Complexity: Nesting │ └─ Too many conditionals → Complexity: Conditional │ ├─ Security concern? │ ├─ SQL injection risk → Security: SQL Injection │ ├─ XSS vulnerability → Security: XSS │ ├─ Mass assignment issue → Security: Mass Assignment │ └─ Outdated gem with CVE → Security: Dependency │ ├─ Outdated code? │ ├─ Rails deprecation warning → Deprecation: Rails │ ├─ Ruby version warning → Deprecation: Ruby │ └─ Deprecated gem API → Deprecation: Gem │ ├─ Performance problem? │ ├─ N+1 query pattern → Performance: N+1 │ ├─ Missing database index → Performance: Index │ ├─ Memory

Find methods longer than 20 lines
awk '
len = NR - start
if (len > 20) print FILENAME ":" name " (" len " lines)"
start = 0
Find classes larger than 150 lines
for file in app/models/*.rb app/services/*.rb; do
if [ "$lines" -gt 150 ]; then
echo "$file: $lines lines"
fi