Codebase Mapper

Analyze a repository to generate CURRENT.md, TARGET.md, and GAPS.md artifacts.

1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/soheunyi/get-research-done --skill codebase-mapper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Codebase Mapper
Source: https://github.com/soheunyi/get-research-done/tree/main/skills/grd-codebase-mapper
Command: npx skills add https://github.com/soheunyi/get-research-done --skill codebase-mapper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze a repository to generate a practical map of current codebase state, intended target shape, and prioritized deltas that guide architecture and implementation work.

Core Features & Use Cases

  • Generates a CURRENT.md capturing present structure, dependencies, and conventions for the repository.
  • Generates a TARGET.md describing the desired architecture and end-state to guide incremental changes.
  • Produces a GAPS.md listing prioritized deltas with impact, confidence, and smallest next actions.
  • Supports optional artifacts such as STACK.md, ARCHITECTURE.md, CONVENTIONS.md, and TESTING.md when requested.

Quick Start

Create the initial CURRENT.md, TARGET.md, and GAPS.md artifacts by running the planner against the repository.

Frequently Asked Questions about Codebase Mapper

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

FAQPage Schema
How do I map my current codebase state to a target architecture?

Codebase mapping for architectural changes involves generating a GAPS.md file that lists prioritized implementation deltas with impact, confidence, and smallest next actions. This bridges the current state and target architecture by providing structured, actionable steps.

What is the best way to plan incremental changes across existing modules?

Planning incremental changes across existing modules requires generating prioritized deltas that guide architecture and implementation work. By analyzing the repository, you produce structured artifacts like CURRENT.md and TARGET.md to guide changes module by module.

Can I document codebase conventions and testing strategies alongside architecture mapping?

Yes, you can document codebase conventions and testing strategies during architecture mapping by generating optional artifacts. The mapping process supports creating supplementary files such as CONVENTIONS.md and TESTING.md alongside the core architecture documents.

When do I need to generate a codebase roadmap for architectural changes?

You need to generate a codebase roadmap for architectural changes when starting from an existing codebase, recovering from drift, or planning modifications across modules. It helps turn current code into a clear map of current state and desired target shape.