yet-another-agent-harness: Skill for Claude Code

Technical Debt Analysis

Investigate the codebase across 8 categories, score each finding by impact and effort, and generate a prioritized TECH_DEBT.md remediation plan. Four categories are analyzed directly; four delegate to specialized skills.

Prerequisite check

git --version 2>/dev/null && git rev-parse --is-inside-work-tree 2>/dev/null

If not in a git repository, warn but proceed — git history analysis will be unavailable but other checks still work.

Step 1: Project context

Gather baseline metrics before analysis:

echo "Project: $(basename $(pwd))"
echo "Files: $(find . -type f -name '*.go' -o -name '*.js' -o -name '*.ts' \
  -o -name '*.py' -o -name '*.rs' -o -name '*.cs' | grep -v node_modules \
  | grep -v vendor | grep -v .git | wc -l)"
echo "Branch: $(git rev-parse --abbrev-ref HEAD 2>/dev/null)"
echo "Last commit: $(git log -1 --format='%h %s' 2>/dev/null)"

Detect project type (Go, Node, Python, .NET, Rust, mixed) from config files present.

Step 2: Delegated categories

For categories covered by specialized skills, delegate or note for future delegation:

Code quality — if the scout skill is available, run it against recently changed files. Scout identifies the top 3 improvement opportunities per file using Impact x Low-Risk scoring.

Linting — if the lint-fix skill is available, run its detection mode (Step 1 only) to identify which linting tools are configured and whether any are missing. Do not run the full fix pipeline.

Security — if the security-audit skill is available, run it for OWASP Top 10 analysis, secrets detection, supply chain assessment, and threat modeling. Include the security score in the tech debt scorecard.

Dependencies — if the dep-upgrade skill is available, run its audit step (Steps 1-2 only) to identify outdated and vulnerable packages with priority categorization. Include the dependency health score in the tech debt scorecard.