from code-archaeologist10
Analyze a repository's history to surface reverts, hotspots, god-objects, and pattern violations before making code changes.
This skill analyzes a codebase's git history to provide risk-aware guidance before modifying code. It detects reverts, frequently changed functions (hotspots), large 'god' files with many dependents, and common pattern adoption across a project. Outputs include risk scores, timelines, pattern statistics, dependency graphs, and recommendations to guide safe edits and design decisions.
Use this skill before fixing bugs, refactoring, or adding features to an existing codebase—especially for unfamiliar folders or modules with substantial commit history. Triggers include: requests to modify code, add features, or investigate 'why' questions about past design choices.
Best suited for code-aware assistants and agents with git and shell access (Claude Code, Codex-style agents, CLI-capable assistants).
This skill has not been reviewed by our automated audit pipeline yet.
