code-archaeologist

Analyze git history to surface code context before edits.

10|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/udaybandaru/code-archaeologist --skill code-archaeologist-udaybandaru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-archaeologist
Source: https://github.com/udaybandaru/code-archaeologist/tree/main
Command: npx skills add https://github.com/udaybandaru/code-archaeologist --skill code-archaeologist-udaybandaru

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about code-archaeologist

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

FAQPage Schema
How do I analyze git history to understand why a codebase looks the way it does?

Analyzing git history involves mining commit logs, detecting hotspots, and tracking dependency evolution to reconstruct past architectural decisions. This surfaces historical context and risk warnings before you edit code.

What is the best way to identify code hotspots and complexity growth before a refactor?

Identifying code hotspots requires analyzing file and function evolution through commit history. This detects complexity growth, contributor patterns, and coupling, providing risk-aware planning context before modifying functions.

How can I detect circular dependencies and architectural pattern violations in a git repository?

Detecting circular dependencies and pattern violations requires dependency and pattern intelligence analysis. This tracks import churn, identifies god objects, and flags required architectural patterns across the codebase history.

Does code history mining work for adding new features to existing modules?

Yes, code history mining works for feature additions by surfacing relevant historical context. It identifies previous failed attempts, mandatory patterns, and required rollout safeguards to reduce risk when modifying existing components.

How do I assess the risk of modifying a function with high revert history?

Assessing modification risk involves analyzing revert history and applying commit weighting to historical context. This determines how cautious your changes should be by highlighting past failures and activity bursts.

Can I trace folder evolution and contributor patterns over time in a git-backed project?

Yes, you can trace folder evolution by reconstructing how a module changed over time. This analysis identifies historical milestones, activity bursts, and contributor patterns to preserve architectural consistency.