.claude/skills/ln-512-tech-debt-cleaner/SKILL.md
Automated tech debt cleanup worker (L3). Reads codebase audit findings, applies safe auto-fixes for low-risk issues (unused imports, dead code, commented-out code, deprecated aliases). Confidence >=90% only. Creates single commit with summary.
npx skillsauth add cbbkrd-tech/jl-finishes ln-512-tech-debt-cleanerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Paths: File paths (
shared/,references/,../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.
Automated cleanup of safe, low-risk tech debt findings from codebase audits.
docs/project/codebase_audit.md (ln-620 output) or ln-511 code quality output| Category | Source Prefix | Risk | Auto-Fix Action | |----------|--------------|------|-----------------| | Unused imports | MNT-DC- | LOW | Delete import line | | Unused variables | MNT-DC- | LOW | Delete declaration | | Unused functions (unexported) | MNT-DC- | LOW | Delete function block | | Commented-out code (>5 lines) | MNT-DC- | LOW | Delete comment block | | Backward-compat shims (>6 months) | MNT-DC- | MEDIUM | Delete shim + update re-exports | | Deprecated aliases | MNT-DC- | LOW | Delete alias line | | Trailing whitespace / empty lines | MNT- | LOW | Trim / collapse |
| Category | Reason | |----------|--------| | DRY violations (MNT-DRY-) | Requires architectural decision on where to extract | | God classes (MNT-GOD-) | Requires domain knowledge for splitting | | Security issues (SEC-) | Requires context-specific fix | | Architecture violations (ARCH-) | Requires design decision | | Performance issues (PERF-) | Requires benchmarking | | Any finding with effort M or L | Too complex for auto-fix |
ln-620 codebase audit completes (user triggers manually)docs/project/codebase_audit.md (ln-620 output)Load findings: Read docs/project/codebase_audit.md. Parse findings from Dead Code section (ln-626 results) and Code Quality section (ln-624 results).
Filter to auto-fixable:
node_modules/, vendor/, dist/, build/, *.min.*, generated code, test fixturesVerify each finding (confidence check):
MANDATORY READ: shared/references/clean_code_checklist.md
For each candidate fix:
a) Read the target file at specified location
b) Confirm the finding still exists (file may have changed since audit)
c) Confirm removal is safe:
Apply fixes (bottom-up within each file):
Verify build integrity:
Per shared/references/ci_tool_detection.md discovery hierarchy: detect and run lint + typecheck commands.
git checkout .), report failureCreate commit:
git add per file, not git add .)chore: automated tech debt cleanup
Removed {N} auto-fixable findings from codebase audit:
- {count} unused imports
- {count} dead functions
- {count} commented-out code blocks
- {count} deprecated aliases
Source: docs/project/codebase_audit.md
Confidence threshold: >=90%
Update audit report:
docs/project/codebase_audit.md:
## Last Automated Cleanup
**Date:** YYYY-MM-DD
**Findings fixed:** N of M auto-fixable
**Skipped:** K (confidence <90% or verification failed)
**Build check:** PASSED / SKIPPED
verdict: CLEANED | NOTHING_TO_CLEAN | BUILD_FAILED
stats:
total_findings: {from audit}
auto_fixable: {filtered count}
applied: {actually fixed}
skipped: {confidence <90 or stale}
reverted: {if build failed, all}
fixes:
- file: "src/utils/helpers.ts"
line: 45
category: "unused_function"
removed: "formatDate()"
finding_id: "MNT-DC-003"
- file: "src/api/v1/auth.ts"
line: 12
category: "deprecated_alias"
removed: "export { newAuth as oldAuth }"
finding_id: "MNT-DC-007"
build_check: PASSED | SKIPPED | FAILED
commit_sha: "abc1234" | null
git add . or git add -A.shared/references/clean_code_checklist.mdshared/references/audit_output_schema.mdshared/templates/codebase_audit_template.mdVersion: 1.0.0 Last Updated: 2026-02-15
testing
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.
development
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
development
Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences.
development
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' or 'involuntary churn.' This skill covers voluntary churn (cancel flows, save offers, exit surveys) and involuntary churn (dunning, payment recovery). For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.