1.4 KiB
1.4 KiB
| description | argument-hint | allowed-tools |
|---|---|---|
| Audit codebase for systemic tech debt - inconsistent patterns that should be unified | <category, e.g., "error-handling", "logging", "api-calls", "auth", or "all"> | Task, Read, Write, Edit, Glob, Grep, Bash |
Audit for systemic tech debt: $ARGUMENTS
Instructions
Load the systemic-debt-auditor skill, then:
If "all" or no category:
High-level scan:
| Category | Variations | Worst Issue | Priority |
|----------|------------|-------------|----------|
| Error Handling | 4 patterns | unwrap in prod | HIGH |
| Logging | 3 patterns | println debug | MEDIUM |
Then ask which to deep dive.
If specific category:
- Survey - Find all variations with grep
- Categorize - Document each pattern
- Identify canonical - Best existing pattern
- Risk assess - CRITICAL > HIGH > MEDIUM > LOW
- Propose plan - Incremental unification
Quick Reference
Error Handling (Go)
grep -rn "panic(" --include="*.go" | wc -l
grep -rn "log.Fatal" --include="*.go" | wc -l
grep -rn "if err != nil" --include="*.go" | wc -l
Logging
grep -rn "fmt.Print" --include="*.go" | wc -l
grep -rn "slog\.\|log\." --include="*.go" | wc -l
Output Requirements
- Patterns found with counts
- Canonical pattern recommendation
- Risk assessment table
- Unification plan (stop bleeding → fix critical → gradual cleanup)
- Enforcement mechanism