cartography

Name: cartography
Availability: InStock
Author: hadenlabs

Map code repositories by computing file hashes and generating per-folder codemaps.

1|Updated Dec 9, 2024

Search Tags:#codebase #hashing #codemap #change-detection #explorer #cartography #repository-mapping

Ready to run

npx skills add https://github.com/hadenlabs/tasks --skill cartography-hadenlabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cartography
Source: https://github.com/hadenlabs/tasks/tree/main/.claude/skills/cartography
Command: npx skills add https://github.com/hadenlabs/tasks --skill cartography-hadenlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Large codebases are hard to understand and onboard without a consistent map of files, dependencies, and responsibilities. Cartography provides a reproducible method to map a repository and generate per-folder codemaps for explorers to fill.

Core Features & Use Cases

Initialize a repository atlas by hashing core files (excluding tests/docs/build artifacts) and creating empty codemaps for every mapped folder.
Detect changes over time and report affected folders to update only necessary codemaps.
Generate a centralized root atlas codemap summarizing mapped directories and integration points for quick orientation.

Quick Start

Initialize the mapping workflow by running cartographer.py init with your project root and include/exclude patterns.

Frequently Asked Questions about cartography

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

FAQPage Schema

How do I generate a codebase map for repository exploration?▼

Compute stable file and folder hashes to create a repository atlas with per-folder codemaps. This codebase mapping excludes tests, docs, and build artifacts, focusing on core files to produce actionable templates for explorers.

What is the best way to track codebase changes for incremental updates?▼

Detect codebase changes by computing file and folder hashes to identify affected directories. This change-detection workflow reports only modified folders, allowing you to update necessary codemaps without remapping the entire repository.

How does repository hashing work for identifying core files?▼

Repository hashing computes stable identifiers for files and folders while respecting gitignore rules. It omits tests, docs, and build artifacts during core file selection, ensuring only essential source files are mapped into the codemap templates.

Can I map a large software project without including test and build artifacts?▼

Yes, repository mapping respects gitignore patterns and explicitly omits tests, docs, and build artifacts when selecting core files. This ensures the generated atlas remains focused on essential source code for software projects of all sizes.

How do I initialize a repository atlas for a new codebase?▼

Initialize the repository atlas by running the init workflow with your project root and include/exclude patterns. This computes initial file and folder hashes and generates empty codemap templates for every mapped directory in the codebase.