repo-atlas

Generate hierarchical codemaps and architectural context for software repositories.

1|Updated Dec 9, 2024
One-click install
npx skills add https://github.com/hadenlabs/tasks --skill repo-atlas-hadenlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-atlas
Source: https://github.com/hadenlabs/tasks/tree/main/.claude/skills/repo-atlas
Command: npx skills add https://github.com/hadenlabs/tasks --skill repo-atlas-hadenlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Maps repositories into codemaps and provides architecture context for engineering teams.

Core Features & Use Cases

  • Language-agnostic repository scanning to generate hierarchical codemaps.
  • Monorepo-aware detection and incremental updates to codemaps.
  • Persist state and reuse existing codemaps to minimize reprocessing.

Quick Start

Map a local repository to generate an initial codemap and maintain incremental updates.

Frequently Asked Questions about repo-atlas

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

FAQPage Schema
How do I generate a codemap for a large monorepo?

Codemapping a monorepo involves language-agnostic repository scanning to detect layouts, compute file hashes, and generate hierarchical architectural context. State is persisted to enable incremental updates and minimize reprocessing.

What is repository architecture mapping and how does it work?

Repository architecture mapping detects repo types and infers domains to produce hierarchical codemaps. It works by scanning projects, computing file hashes, and persisting state to an architecture file for reuse.

Can I use this to scan multi-repo layouts and language-agnostic projects?

Yes, you can scan multi-repo layouts and language-agnostic projects. The Skill handles repository type detection and domain inference across diverse project structures to generate codemaps.

How do I maintain incremental updates to a repository codemap?

To maintain incremental codemap updates, the Skill computes file hashes and persists state to a cartography file. This allows it to reuse existing codemaps and only regenerate root or folder maps for changed files.

Where does the generated repository architecture state persist?

Generated repository architecture state persists to the .slim/cartography.json file. This file stores computed file hashes and codemap data to support incremental updates without full reprocessing.