acquire-codebase-knowledge

Generate seven documentation templates from verifiable repository data.

1|1|Updated May 3, 2026

Search Tags:#architecture #documentation #onboarding #codebase #discovery #mapping #repo

Ready to run

npx skills add https://github.com/matt-riley/agent-skills --skill acquire-codebase-knowledge-matt-riley

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: acquire-codebase-knowledge
Source: https://github.com/matt-riley/agent-skills/tree/main/skills/acquire-codebase-knowledge
Command: npx skills add https://github.com/matt-riley/agent-skills --skill acquire-codebase-knowledge-matt-riley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map, document, and onboard to an existing codebase by generating a canonical seven-document knowledge set derived entirely from verifiable repository data.

Core Features & Use Cases

Automatic generation of seven documentation templates: STACK.md, STRUCTURE.md, ARCHITECTURE.md, CONVENTIONS.md, INTEGRATIONS.md, TESTING.md, CONCERNS.md, all populated with evidence from repo files.
Use-case scenarios include onboarding new engineers, performing repo-wide architecture discovery, and aligning governance with project standards.
Strict provenance and traceability: every claim is anchored to specific files or terminal outputs; unknowns are clearly marked.

Quick Start

Generate the seven codebase documentation templates from the repository using only verifiable files and terminal outputs.

Frequently Asked Questions about acquire-codebase-knowledge

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

FAQPage Schema

What is the best way to document repository structure for new contributors?▼

Onboard new engineers by generating a structured knowledge bundle from verifiable repository data. This creates a canonical seven-document set covering stack, structure, conventions, and testing to accelerate contributor alignment.

How does repository-wide discovery mapping work for unknown codebases?▼

Map codebase integrations and conventions safely by anchoring every claim to specific files or terminal outputs. The generated documentation strictly avoids unsupported inferences and clearly marks any unknown elements.

Can I map codebase integrations and conventions without making unsupported inferences?▼

Repository-wide discovery mapping works by scanning verifiable files and terminal outputs to populate seven documentation templates. It derives architecture, structure, and testing facts directly from the repo, ensuring full traceability.

How do I generate architecture documentation for an existing codebase?▼

Codebase architecture discovery generates seven markdown templates: STACK.md, STRUCTURE.md, ARCHITECTURE.md, CONVENTIONS.md, INTEGRATIONS.md, TESTING.md, and CONCERNS.md, all populated with evidence from repository files.

What templates are generated during codebase architecture discovery?▼

You do not need external dependencies to map and document your codebase. The discovery process relies solely on verifiable repository files and terminal outputs to generate the structured documentation set.

Do I need external dependencies to map and document my codebase?▼

Avoid automated codebase documentation generation if your repository lacks sufficient source files or terminal outputs to verify claims, as the process strictly requires traceable evidence and flags unknowns.