---
name: Codebase Scan
slug: codebase-scan
category: Automation
description: Codebase Scan creates a high-level map of a project’s directories, entry points, configs, and core modules. Use it during bootstrap or onboarding before deeper architecture extraction.
github: "https://github.com/digipulse-engineering/GAAI-framework/tree/main/.gaai/core/skills/cross/codebase-scan"
language: Shell
stars: 161
forks: 27
install: "npx degit https://github.com/digipulse-engineering/GAAI-framework/tree/main/.gaai/core/skills/cross/codebase-scan ~/.claude/skills/codebase-scan"
installs_to: ~/.claude/skills/codebase-scan
source_path: .gaai/core/skills/cross/codebase-scan/SKILL.md
collection_size: 25
category_size: 2226
collection_url: "https://dirskills.com/collections/Fr-e-d/GAAI-framework"
added: 2026-09-08T05:36:20.303Z
last_synced: 2026-09-08T05:36:20.303Z
canonical_url: "https://dirskills.com/skills/codebase-scan"
---

# Codebase Scan

Codebase Scan creates a high-level map of a project’s directories, entry points, configs, and core modules. Use it during bootstrap or onboarding before deeper architecture extraction.

**Install:**

```bash
npx degit https://github.com/digipulse-engineering/GAAI-framework/tree/main/.gaai/core/skills/cross/codebase-scan ~/.claude/skills/codebase-scan
```

## README

# 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.**