code-archaeology

Analyze unfamiliar codebases to map topology and data flow.

Updated May 5, 2026

Search Tags:#git #architecture #onboarding #refactoring #codebase #analysis

Ready to run

npx skills add https://github.com/iani-kuli/harness_bro --skill code-archaeology-iani-kuli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-archaeology
Source: https://github.com/iani-kuli/harness_bro/tree/main/.claude/skills/curated/code-archaeology
Command: npx skills add https://github.com/iani-kuli/harness_bro --skill code-archaeology-iani-kuli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the cognitive overload of joining an unfamiliar project by providing a structured, systematic approach to exploring and documenting unknown codebases.

Core Features & Use Cases

Topology Mapping: Automatically generates a high-level view of project structure and identifies primary entry points.
Hotspot Analysis: Uses git history to highlight the most frequently modified files, indicating critical areas of the system.
Use Case: When assigned to a legacy project, use this Skill to quickly identify the main data flow, key abstractions, and potential technical debt without manually reading every file.

Quick Start

Use the code-archaeology skill to analyze the current directory and provide an architectural summary of the codebase.

Frequently Asked Questions about code-archaeology

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

FAQPage Schema

How do I analyze an unfamiliar codebase to understand its architecture?▼

You can analyze an unfamiliar codebase by mapping project topology and data flow. This approach identifies primary entry points, architectural patterns, and high-churn files to build a mental model of the repository structure.

What is the best way to identify high-churn files in a legacy codebase?▼

Identifying high-churn files in a legacy codebase involves analyzing git logs. This highlights the most frequently modified files, indicating critical areas of the system and potential technical debt without manually reading every file.

How do I map project topology and data flow for rapid onboarding?▼

Mapping project topology for rapid onboarding requires automatically generating a high-level view of the project structure. This identifies main data flows and key abstractions to reduce the cognitive overload of joining an unfamiliar project.

Can I use git history to assess technical debt in a codebase?▼

Yes, you can use git history to assess technical debt in a codebase. By highlighting frequently modified files, git logs indicate critical areas of the system and help locate potential technical debt during legacy code assessment.

Do I need any special dependencies to perform a read-only diagnostic summary of a repository?▼

No special dependencies are required to perform a read-only diagnostic summary of a repository. The analysis utilizes standard Unix utilities and git logs to provide a structural summary without modifying the codebase.

What are the limitations of using standard Unix utilities for codebase analysis?▼

The limitation of using standard Unix utilities for codebase analysis is that it provides a read-only diagnostic summary of repository structure. It offers a high-level view and identifies hotspots, but does not modify code or replace deep manual review.