codebase-scan

Generate a codebase tree and key files list from a repository.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill codebase-scan-petrsimonidesxart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-scan
Source: https://github.com/petrSimonidesXart/xPmGateway/tree/main/.gaai/core/skills/cross/codebase-scan
Command: npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill codebase-scan-petrsimonidesxart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a concise, structured view of a repository's surface, exposing the directory layout, key entry points, and module boundaries to accelerate understanding and planning during bootstrap and architecture extraction.

Core Features & Use Cases

  • Recursively enumerate directories and files to generate a complete project tree.
  • Identify entry points, configuration files, manifests, and core modules.
  • Highlight likely architecture boundaries to support architecture extraction workflows.
  • Output the structured results as codebase_tree and key_files_list for downstream analysis.

Quick Start

Provide your repository to the skill to generate a structured codebase map.

Frequently Asked Questions about codebase-scan

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

FAQPage Schema
How do I map the project structure and architectural boundaries of an existing repository?

To map a repository's structure, you recursively enumerate directories and files to generate a complete project tree, identifying entry points, manifests, and core modules to expose architectural boundaries and accelerate onboarding.

What is the best way to identify entry points and core modules during codebase onboarding?

The best way to identify entry points during codebase onboarding is to generate a structured codebase map that highlights configuration files, manifests, and core modules, providing a concise view of the repository's surface.

Can I extract a codebase tree from a repository before starting architecture extraction?

Yes, you can extract a codebase tree and a key files list from a repository prior to architecture extraction. This maps directories and boundaries, providing structured output suitable for downstream architecture-extract workflows.

Does codebase mapping work for understanding directory layout during project bootstrap?

Codebase mapping works effectively during project bootstrap by recursively enumerating directories and files to generate a complete project tree, exposing the directory layout and likely architecture boundaries for planning.

What outputs do I get from mapping a repository's architectural boundaries?

Mapping a repository's architectural boundaries yields a structured codebase_tree and a key_files_list. These outputs detail the directory layout, entry points, and core modules, making them suitable for downstream analysis.