autopsy

# autopsy ## Purpose Full codebase health assessment for legacy projects. Autopsy analyzes complexity, dependency coupling, dead code, tech debt, and git hotspots to produce a health score per module and a prioritized rescue plan. Uses opus for deep analysis quality. ## Called By (inbound) - `rescue` (L1): Phase 0 RECON — assess damage before refactoring - `onboard` (L2): when project appears messy during onboarding - `audit` (L2): Phase 3 code quality and complexity assessment - `incident` (L2): root cause analysis after containment ## Calls (outbound) - `scout` (L2): deep structural scan — files, LOC, entry points, imports - `research` (L3): identify if tech stack is outdated - `trend-scout` (L3): compare against current best practices - `journal` (L3): record health assessment findings ## Execution Steps ### Step 0 — Repo intelligence (if GitHub-hosted) If the project is a GitHub repository, gather repo-level metrics before diving into code: ```bash # Fetch via GitHub API (requires gh CLI or curl + GITHUB_TOKEN) gh api repos/{owner}/{repo} --jq '{stars: .stargazers_count, forks: .forks_count, open_issues: .open_issues_count, license: .license.spdx_id, language: .language, topics: .topics, created: .created_at, pushed: .pushed_at}' # Contributor count and top contributors gh api repos/{owner}/{repo}/contributors --jq 'length' gh api repos/{owner}/{repo}/contributors --jq '.[0:5] | .[] | "\(.login): \(.contributions)"' # Commit frequency (last 52 weeks) gh api r...