codebase-scan

$npx mdskill add Fr-e-d/GAAI-framework/codebase-scan

Maps project structure and identifies key architectural components.

  • Reveals unknown project structure during onboarding or bootstrap.
  • Relies on filesystem access to recursively list directories and files.
  • Identifies entry points, configs, manifests, and core modules.
  • Outputs a structured directory tree and list of key files.

SKILL.md

.github/skills/codebase-scanView on GitHub ↗
---
name: codebase-scan
description: Create a high-level map of the project structure and identify architectural pillars, entry points, and module boundaries. Activate at Bootstrap initialization or before architecture extraction.
license: ELv2
compatibility: Works with any filesystem-based AI coding agent
metadata:
  author: gaai-framework
  version: "1.0"
  category: cross
  track: cross-cutting
  id: SKILL-CODEBASE-SCAN-001
  updated_at: 2026-02-26
  status: stable
inputs:
  - repository/**
outputs:
  - codebase_tree
  - key_files_list
---

# Codebase Scan

## Purpose / When to Activate

Activate:
- During Bootstrap initialization (before architecture extraction)
- When onboarding GAAI onto an existing codebase
- When the project structure is unknown

---

## Process

1. Recursively list directories and files
2. Identify entry points, config files, manifests, and core modules
3. Highlight likely architecture boundaries
4. Output a structured project tree and key file list

---

## Outputs

**`codebase_tree`** — structured directory tree with annotations for key files

**`key_files_list`** — list of significant files: entry points, configs, manifests, core modules, test runners

---

## Quality Checks

- Repository structure is fully visible
- Core technical pillars are identified
- No blind spots remain
- Output is structured for use by `architecture-extract`

---

## Non-Goals

This skill must NOT:
- Interpret architecture decisions (use `architecture-extract`)
- Read file contents in depth
- Make recommendations

**Maps the terrain. Does not interpret it.**

More from Fr-e-d/GAAI-framework

SkillDescription
abort-safe-handlerOrchestrator-level Stage 4 entry gate for /gaai:bootstrap. Presents a pre-loop "Skip Q&A entirely" option, delegates to qa-loop-ui when the user proceeds, and returns a unified abort_safe_result with telemetry on every path. Guarantees no partial state on skip or abort.
ambiguity-detectorTakes surface scan results, optional LLM synthesis open-question entries, and optional tree-sitter AST signals to score project ambiguities (1-10). Outputs structured ambiguity_feed for smart-question-generator. Pure heuristic — no LLM calls. Designed for Stage 3.5 of the /gaai:bootstrap pipeline (between LLM synthesis and Q&A).
approach-evaluationResearch industry standards and best practices, identify viable approaches for a given technical or architectural problem, and produce a structured factual comparison against project-specific constraints. Reports options — does not decide.
architecture-extractConvert raw project structure into clear architectural understanding — module boundaries, data flows, service relationships, and architectural patterns. Activate after codebase-scan during Bootstrap.
bootstrap-llm-synthesisConstruct the LLM synthesis prompt from project surface scan + optional tree-sitter context + optional Q&A answers. Call the LLM. Parse and validate the response into 6-8 structured memory entries with clarity tags and source traceability. Used as Stage 3 of the /gaai:bootstrap pipeline.
bootstrap-memory-ingest-cloudWrite structured memory entries to the Cloud workspace via gaai_memory.store MCP tool with source='bootstrap'. Loops over entries from bootstrap-llm-synthesis, calls the tool per entry, collects success/fail counts. Used as Stage 5 of the /gaai:bootstrap pipeline (Cloud path only).
browser-journey-testValidate user stories by simulating real user journeys in a live browser against deployed application. Activate after implementation to verify actual user experience against acceptance criteria, not just code logic.
build-agents-indexScan all agent and sub-agent definition files in .gaai/core/agents/, extract YAML frontmatter, merge with specialists.registry.yaml, and generate a derived agents-index.yaml at .gaai/core/agents/agents-index.yaml. Activate after adding, modifying, or removing any agent, sub-agent, or specialist entry.
build-skills-indexScan SKILL.md files in .gaai/core/skills/ and .gaai/project/skills/, extract YAML frontmatter, and regenerate separate skills indices for each layer. Core index ships with the OSS framework; project index is project-specific.
ci-watch-and-fixWatch GitHub Actions CI after PR creation, detect failures, extract logs, apply minimal fixes, and re-push — keeping the delivery session alive until CI resolves or escalating after 3 cycles. Activate immediately after gh pr create and before marking the story done.