What problem does it solve?
Code Archaeologist helps you understand why a codebase looks the way it does before you make changes, so you can avoid repeating past mistakes, reduce risk, and preserve architectural consistency.
Core Features & Use Cases
- Folder evolution analysis: Reconstruct how a module or component changed over time, including milestones, activity bursts, and contributor patterns.
- File and function evolution: Identify hotspots, complexity growth, coupling, and detailed history for specific functions before touching them.
- Dependency and pattern intelligence: Detect circular dependencies, god objects, import churn, required architectural patterns, and pattern violations.
- Risk-aware planning: Use revert history, commit weighting, and historical context to decide how cautious a change should be.
- Use case: If you are about to refactor a streaming handler or add OAuth support to an auth module, this Skill tells you what failed before, what patterns are mandatory, and what tests or rollout safeguards you should plan.
Quick Start
Ask the AI to analyze the target folder or file with the Code Archaeologist skill before editing so it can return historical context, risk warnings, and implementation guidance.