rune-autopsy

Analyzes codebase complexity, dependencies, dead code, and git history to produce a health score and rescue plan.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dangvu008/VietTruyen --skill rune-autopsy-dangvu008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rune-autopsy
Source: https://github.com/dangvu008/VietTruyen/tree/main/.agents/skills/rune-autopsy
Command: npx skills add https://github.com/dangvu008/VietTruyen --skill rune-autopsy-dangvu008

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Legacy codebases accumulate hidden technical debt, dead code, and risky hotspots that teams cannot quantify. This Skill performs a full codebase health assessment so you know exactly which modules are critical before starting any refactoring or rescue effort. ## Core Features & Use Cases - Module Health Scoring: Scores every module 0-100 across six dimensions (complexity, test coverage, documentation, dependencies, code smells, maintenance) and assigns a risk tier from healthy to critical. - Git Archaeology: Identifies hotspot files, stale files untouched for over a year, dead code candidates, commit velocity trends, and bus factor from git history and GitHub API metrics. - Prioritized Rescue Plan: Generates a RESCUE-REPORT.md with a Mermaid dependency graph, language distribution chart, and a ranked surgery queue so refactoring effort targets the highest-impact modules first. - Use Case: When inheriting an unfamiliar legacy project, run the autopsy to get a quantified health report with confidence levels before deciding what to refactor. ## Quick Start Ask the agent to run a full codebase health assessment on this project and generate a rescue report with module scores and a prioritized refactoring queue.

Frequently Asked Questions about rune-autopsy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assess the health of a legacy codebase before refactoring?

Run a structured autopsy that scans every module for cyclomatic complexity, nesting depth, test coverage, and coupling, then scores each module 0-100 across six weighted dimensions. The output is a prioritized rescue report ranking the worst modules first.

How to find dead code and hotspot files using git history?

Use git log with name-only output to count change frequency per file for hotspots, and diff against commits from a year ago to find stale files. A file is likely dead code if nothing imports it, no config references it, and it was last modified over six months ago.

What metrics indicate a codebase has high technical debt?

Key signals include cyclomatic complexity above 20, test coverage below 20 percent, files over 500 lines with many importers, circular dependencies, and commit activity below one commit per week. A bus factor of one contributor is also a critical risk.

Does codebase health analysis work for projects without git history?

Yes, but findings carry lower confidence. Without git data, hotspot and staleness analysis is skipped, and health scores rely on direct code metrics only, which the report marks as medium or low confidence accordingly.

What are the limitations of automated codebase health scoring?

The assessment only diagnoses and prioritizes; it does not refactor code itself. Scores for unreadable files such as binaries or generated code are low confidence, and dynamic imports or plugin-based loading can cause false positives in dead code detection.