community example · Use or study
acquire-codebase-knowledge
Map an existing repository for onboarding with evidence-linked architecture and working-practice notes.
github/awesome-copilotskills/acquire-codebase-knowledge/SKILL.md
Before you use it
- Input
- An explicitly authorized codebase-discovery task, the repository boundary and an optional focus such as architecture or testing.
- Expected output
- The source specifies seven documents covering stack, structure, architecture, conventions, integrations, testing and concerns, with file evidence and unresolved questions.
- Prerequisites
- The source declares Python 3.8+, Git and a scan helper. That helper, referenced templates and checkpoints were not read in this review; their behavior, coverage and output effects remain unverified. Do not provide secrets or permit a broad scan merely to fix one file.
Client setup and runtime behavior are not verified here; client installation is not individually established. The use notes below describe source preparation, inputs and limits.
Publisher documentation, static file observations and environment tests are different kinds of evidence. Runtime behavior has not been observed.
Use this method
Source-based preparation, not an installation or a completed run. Nothing is executed here.
- Good fit for
- Studying or preparing an explicit repository onboarding and documentation task with a controlled scope.
- Not for / limits
- Not a prerequisite for every bug fix or a verified scanner. Helper bodies and supporting tree remain unreviewed; cross-platform support and scan coverage are publisher statements, not runtime observations.
- Prepare
- Decide whether repository-wide discovery is really the task and define the allowed files, exclusions and output locations before using the instructions.
- Apply
- Read the referenced scan code, templates and inquiry checkpoints yourself before approving a run; they are outside this review's inspected files.
- Check
- Check each resulting claim against its file evidence and preserve unknowns and questions about team intent. Review differences between stated design and observed implementation.
Sources read for this note
These exact files were read as text at the displayed commit. Other files and external tools were not reviewed. A repository LICENSE observation does not confirm Skill-specific applicability or dependency rights.
- skills/acquire-codebase-knowledge/SKILL.md ↗
Read 2026-09-10T10:33:30.629Z
7ca01711e1615171b26ce9e2729bedf041348d7fd0f24bc04e0d400dc93e41b9 - LICENSE ↗
Read 2026-09-10T10:33:31.265Z
e32449d23085399adc1222f7a17408b730550258e51627c153cb108ca9955823
Study the method
Study how declared project intent is compared with file evidence and how focus mode preserves unknowns outside its scope. The instruction's seven-document target is not proof those documents were generated or validated.
File and folder counts are unknown, not zero.
The supporting file list has not been read for this source. Open the source directory to inspect it.
Zero files in scripts/ does not mean no execution, network access or file writes. Markdown and other folders may describe or contain executable behavior.
Source version and requirements
- Observed
- 2026-09-08T11:55:57.465Z
- Source commit
- f38fb6cf039b835990d0f49dc161d7c2af99ef69
- Content SHA-256
- 7ca01711e1615171b26ce9e2729bedf041348d7fd0f24bc04e0d400dc93e41b9
- License
- Unknown
- Author attribution
- Repository owner: github. Individual authorship is not independently established.
This page describes a pinned source snapshot, not the latest repository state. Changes after this commit have not been reconciled here. A repository license does not necessarily cover external models, datasets or services.
Open current repository ↗