gsd-map-codebase

Coordinate parallel analysis agents to produce a structured codebase map.

Updated May 22, 2026
One-click install
npx skills add https://github.com/yusaduymaz/loexai --skill gsd-map-codebase-yusaduymaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-map-codebase
Source: https://github.com/yusaduymaz/loexai/tree/main/.codex/skills/gsd-map-codebase
Command: npx skills add https://github.com/yusaduymaz/loexai --skill gsd-map-codebase-yusaduymaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an unfamiliar repository into a structured, shareable codebase map so teams can understand what exists, how it fits together, and where the key risks are without manually reading every file.

Core Features & Use Cases

  • Parallel codebase exploration: Coordinates multiple mapper agents to inspect different aspects of a project at the same time.
  • Structured documentation output: Produces a complete .planning/codebase set covering stack, architecture, structure, conventions, testing, integrations, and concerns.
  • Use Case: Use it when onboarding to a brownfield repository, preparing for a refactor, or refreshing project intelligence after major changes.

Quick Start

Ask the gsd-map-codebase skill to analyze the current repository and generate the full .planning/codebase documentation set.

Frequently Asked Questions about gsd-map-codebase

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

FAQPage Schema
How do I map an unfamiliar codebase for onboarding?

To map an unfamiliar codebase for onboarding, coordinate parallel mapper agents to inspect the repository and generate structured .planning/codebase documents covering stack, architecture, conventions, testing, and integrations simultaneously.

What is the best way to document an existing repository's architecture?

Documenting an existing repository's architecture is best done by running parallel mapper agents that analyze the codebase and write structured planning documents, capturing the stack, structure, conventions, and key risks without manually reading every file.

Can I analyze a brownfield repository to prepare for a major refactor?

Yes, you can analyze a brownfield repository to prepare for a refactor by using parallel agents to collect repository intelligence, identifying existing conventions, integrations, and architectural concerns before making structural changes.

Does codebase mapping work without manually reading every file?

Codebase mapping works without manually reading every file by coordinating multiple mapper agents to explore different aspects of the project in parallel, minimizing context usage while capturing the complete repository structure and conventions.

What documentation structure is generated when mapping a codebase?

Mapping a codebase generates a structured .planning/codebase documentation set that captures the project stack, architecture, directory structure, coding conventions, testing setup, external integrations, and identified concerns.