Download for MacApple silicon, macOS 14+
Skill

acquire-codebase-knowledge

@github Updated 2026-10-30

Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.

agent-skillsagentsaiawesomecustom-agentsgithub-copilothacktoberfestprompt-engineering

Install

With your agent

Install OMGSkills skill "github/awesome-copilot:acquire-codebase-knowledge" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/github/awesome-copilot /tmp/awesome-copilot && ln -s /tmp/awesome-copilot/skills/acquire-codebase-knowledge ~/.claude/skills/acquire-codebase-knowledge

From README

Acquire Codebase Knowledge Produces seven populated documents in docs/codebase/ covering everything needed to work effectively on the project. Only document what is verifiable from files or terminal output — never infer or assume. Output Contract (Required) Before finishing, all of the following must be true: Exactly these files exist in docs/codebase/: STACK.md, STRUCTURE.md, ARCHITECTURE.md, CONVENTIONS.md, INTEGRATIONS.md, TESTING.md, CONCERNS.md. Every claim is traceable to source files, config, or terminal output. Unknowns are marked as [TODO]; intent-dependent decisions are marked [ASK USER]. Every document includes a short "evidence" list with concrete file paths. Final response includes numbered [ASK USER] questions and intent-vs-reality divergences. Workflow Copy and track this checklist: Focus Area Mode If the user supplies a focus area (for example: "architecture only" or "testing and concerns"): Always run Phase 1 in full. Fully complete focus-area documents first.