All skills
github avatar

/acquire-codebase-knowledge

@9ce8148 official
by githubgithub/awesome-copilot40k stars
5,040

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.

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/acquire-codebase-knowledge

This session only. Nothing lands on disk.

assetstemplatesTESTING.md

≈343 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Testing Patterns

Core Sections (Required)

1) Test Stack and Commands

  • Primary test framework: [NAME + VERSION]
  • Assertion/mocking tools: [TOOLS]
  • Commands:
[run all tests]
[run unit tests]
[run integration/e2e tests]
[run coverage]

2) Test Layout

  • Test file placement pattern: [co-located/tests folder/etc]
  • Naming convention: [pattern]
  • Setup files and where they run: [paths]

3) Test Scope Matrix

Scope Covered? Typical target Notes
Unit [yes/no] [modules/services] [notes]
Integration [yes/no] [API/data boundaries] [notes]
E2E [yes/no] [user flows] [notes]

4) Mocking and Isolation Strategy

  • Main mocking approach: [module/class/network]
  • Isolation guarantees: [what is reset and when]
  • Common failure mode in tests: [short note]

5) Coverage and Quality Signals

  • Coverage tool + threshold: [value or TODO]
  • Current reported coverage: [value or TODO]
  • Known gaps/flaky areas: [list]

6) Evidence

  • [path/to/test-config]
  • [path/to/representative-test-file]
  • [path/to/ci-or-coverage-config]

Extended Sections (Optional)

Add only when needed:

  • Framework-specific suite patterns
  • Detailed mock recipes per dependency type
  • Historical flaky test catalog
  • Test performance bottlenecks and optimization ideas

Source: SKILL.md on GitHub

No alerts15d4 checks · Risk SAFE
  • Gen Agent Trust Hub15d

    This skill facilitates codebase onboarding by scanning local project files and git history to generate documentation. It is generally safe and authored by a trusted vendor, but it carries an inherent low risk of indirect prompt injection if the analyzed codebase contains malicious instructions designed to influence the documentation process.

  • Socket15d

    No alerts

  • Snyk15d

    Risk: LOW · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 9ce8148. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 2 weeks ago
Other metadata
compatibility
Cross-platform. Requires Python 3.8+ and git. Run scripts/scan.py from the target project root.
metadata
{
  "version": "1.3",
  "enhancements": [
    "Multi-language manifest detection (25+ languages supported)",
    "CI/CD pipeline detection (10+ platforms)",
    "Container & orchestration detection",
    "Code metrics by language",
    "Security & compliance config detection",
    "Performance testing markers"
  ]
}
argument-hint
Optional: specific area to focus on, e.g. "architecture only", "testing and concerns"

README badge

README badge for github/awesome-copilot/acquire-codebase-knowledge

Scans a codebase with a Python script to extract stack, structure, architecture, conventions, integrations, testing setup, and known concerns, then populates seven markdown documents in docs/codebase/ with verified facts only. Targets onboarding scenarios where a developer or agent needs to understand an unfamiliar repository quickly.

Generated from the current SKILL.md.

Does this skill work with monorepos?
Yes. The skill detects workspaces and packages directories, and maps each sub-package separately with independent dependencies and conventions.
What languages and platforms does this support?
Cross-platform (Windows, macOS, Linux). Requires Python 3.8+, git, and detects 25+ programming languages. Run scripts/scan.py from the target project root.
Does this document generated code and build artifacts?
No. The skill documents only source conventions and patterns, explicitly avoiding dist/, build/, generated/, .next/, out/, and __pycache__ directories.
What happens if the skill can't determine something about the codebase?
Unknown items are marked [TODO]. If the answer requires team intent or context, it is marked [ASK USER] and presented as a numbered question at the end.
What output does this skill produce?
Seven documented files in docs/codebase/: STACK.md, STRUCTURE.md, ARCHITECTURE.md, CONVENTIONS.md, INTEGRATIONS.md, TESTING.md, and CONCERNS.md, with evidence trails to source files.

Generated from the current SKILL.md. These answers refresh after source changes.