AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

acquire-codebase-knowledge

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.

Original source
github
License
MIT
Pinned revision
5269f7ea2d6c3a9bfda5ed878b6726cf509121fd

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read github--acquire-codebase-knowledge at revision 5269f7ea2d6c3a9bfda5ed878b6726cf509121fd, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 10

assets/templates/TESTING.md

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