shine-map-codebase

Name: shine-map-codebase
Availability: InStock
Author: diShine

Map existing codebases into a structured seven-document codebase map.

1|Updated Apr 15, 2026

Search Tags:#automation #documentation #onboarding #codebase #brownfield #code-review #mapping

Ready to run

npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-map-codebase

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: shine-map-codebase
Source: https://github.com/diShine-digital-agency/SHINE-Code-System/tree/main/skills/shine-map-codebase
Command: npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-map-codebase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map existing codebases to a structured, multi-document representation using parallel shine-codebase-mapper agents, enabling faster onboarding and governance for brownfield projects.

Core Features & Use Cases

Parallel mapping: Spawns multiple agents to explore areas of the codebase and write standardized documents under .planning/codebase/.
Incremental context: Can load existing state from .planning/STATE.md to refresh the map.
Use Case: Before a major refactor or onboarding to an unfamiliar repository, generate a complete codebase map.

Quick Start

Execute the map-codebase skill to create the .planning/codebase/ folder and produce the seven documents.

Frequently Asked Questions about shine-map-codebase

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

FAQPage Schema

How do I map an existing codebase for onboarding to an unfamiliar project?▼

A codebase map is a structured, seven-document representation of an existing repository's architecture and logic. It helps developers understand unfamiliar codebases faster by providing standardized documentation generated through parallel agent exploration under the .planning/codebase/ directory.

How do I update codebase documentation after major changes to a brownfield project?▼

To update codebase documentation after major changes, the skill loads incremental context from an existing .planning/STATE.md file. It then spawns parallel shine-codebase-mapper agents to refresh the seven-document map, ensuring the architectural representation stays synchronized with the updated brownfield codebase.

Do I need any external dependencies to generate a codebase map?▼

No external dependencies are required to generate a codebase map. The skill operates independently by coordinating four internal parallel agents to scan the repository and write the seven standardized documents, requiring only the existing codebase files to analyze.

When should I use parallel codebase mapping instead of manual documentation?▼

Parallel codebase mapping is ideal for brownfield projects before initialization, after major refactors, or during onboarding to unfamiliar repositories. It automates documentation by spawning multiple agents simultaneously, producing a comprehensive seven-document map faster than manual review of complex codebases.