Agent skill
codebase-scan
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.
Install this agent skill to your Project
npx add-skill https://github.com/Fr-e-d/GAAI-framework/tree/main/.gaai/core/skills/cross/codebase-scan
Metadata
Additional technical details for this skill
- id
- SKILL-CODEBASE-SCAN-001
- track
- cross-cutting
- author
- gaai-framework
- status
- stable
- version
- 1.0
- category
- cross
- updated at
- 1772064000
SKILL.md
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
- Recursively list directories and files
- Identify entry points, config files, manifests, and core modules
- Highlight likely architecture boundaries
- 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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
ci-watch-and-fix
Watch 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.
qa-review
Validate that implemented code fully satisfies Story acceptance criteria, respects rules, and introduces no regressions. This is the hard quality gate — no pass means no delivery. Activate after implementation is complete.
compose-team
Assemble the context bundles for each sub-agent based on evaluate-story output. Produces spawn-ready packages for Planning, Implementation, QA, or MicroDelivery sub-agents. Activate after evaluate-story, before spawning any sub-agent.
coordinate-handoffs
Validate sub-agent handoff artefacts, sequence phase transitions, and manage retry and escalation logic. Activate after each sub-agent terminates to determine next action.
implement
Generate correct, minimal, maintainable code that satisfies a validated Story's acceptance criteria against an execution plan. Activate when a Story is validated, a plan exists, and all prerequisites are unambiguous.
delivery-high-level-plan
Transform validated Stories into a clear, minimal, governed execution plan. Used by the Planning Sub-Agent as the first planning pass before prepare-execution-plan for Tier 2/3, or as the sole planning output for simple Stories.
Didn't find tool you were looking for?