Skill0 repo starsupdated yesterday

mindforge-map-codebase

The mindforge-map-codebase skill deploys four parallel agent mappers to analyze an existing codebase and generate seven structured documents in .planning/codebase/, including architecture, technology stack, conventions, and concerns. Use this before initializing brownfield projects, after significant code changes, when onboarding to unfamiliar codebases, or before major refactoring efforts to establish current state understanding.

View source Repository: MindForge

Install in Claude Code

Copy

git clone --depth 1 https://github.com/sairam0424/MindForge /tmp/mindforge-map-codebase && cp -r /tmp/mindforge-map-codebase/.agent/skills/mindforge-map-codebase ~/.claude/skills/mindforge-map-codebase

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

<objective>
Analyze existing codebase using parallel mindforge-codebase-mapper agents to produce structured codebase documents.

Each mapper agent explores a focus area and **writes documents directly** to `.planning/codebase/`. The orchestrator only receives confirmations, keeping context usage minimal.

Output: .planning/codebase/ folder with 7 structured documents about the codebase state.
</objective>

<execution_context>
@.agent/workflows/mindforge-map-codebase.md
</execution_context>

<context>
Focus area: $ARGUMENTS (optional - if provided, tells agents to focus on specific subsystem)

**Load project state if exists:**
Check for .planning/STATE.md - loads context if project already initialized

**This command can run:**
- Before /mindforge-new-project (brownfield codebases) - creates codebase map first
- After /mindforge-new-project (greenfield codebases) - updates codebase map as code evolves
- Anytime to refresh codebase understanding
</context>

<when_to_use>
**Use map-codebase for:**
- Brownfield projects before initialization (understand existing code first)
- Refreshing codebase map after significant changes
- Onboarding to an unfamiliar codebase
- Before major refactoring (understand current state)
- When STATE.md references outdated codebase info

**Skip map-codebase for:**
- Greenfield projects with no code yet (nothing to map)
- Trivial codebases (<5 files)
</when_to_use>

<process>
1. Check if .planning/codebase/ already exists (offer to refresh or skip)
2. Create .planning/codebase/ directory structure
3. Spawn 4 parallel mindforge-codebase-mapper agents:
   - Agent 1: tech focus → writes STACK.md, INTEGRATIONS.md
   - Agent 2: arch focus → writes ARCHITECTURE.md, STRUCTURE.md
   - Agent 3: quality focus → writes CONVENTIONS.md, TESTING.md
   - Agent 4: concerns focus → writes CONCERNS.md
4. Wait for agents to complete, collect confirmations (NOT document contents)
5. Verify all 7 documents exist with line counts
6. Commit codebase map
7. Offer next steps (typically: /mindforge-new-project or /mindforge-plan-phase)
</process>

<success_criteria>
- [ ] .planning/codebase/ directory created
- [ ] All 7 codebase documents written by mapper agents
- [ ] Documents follow template structure
- [ ] Parallel agents completed without errors
- [ ] User knows next steps
</success_criteria>