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/CONCERNS.md

Codebase Concerns

Core Sections (Required)

1) Top Risks (Prioritized)

| Severity | Concern | Evidence | Impact | Suggested action | |----------|---------|----------|--------|------------------| | [high/med/low] | [issue] | [file or scan output] | [impact] | [next action] |

2) Technical Debt

List the most important debt items only.

| Debt item | Why it exists | Where | Risk if ignored | Suggested fix | |-----------|---------------|-------|-----------------|---------------| | [item] | [reason] | [path] | [risk] | [fix] |

3) Security Concerns

| Risk | OWASP category (if applicable) | Evidence | Current mitigation | Gap | |------|--------------------------------|----------|--------------------|-----| | [risk] | [A01/A03/etc or N/A] | [path] | [what exists] | [what is missing] |

4) Performance and Scaling Concerns

| Concern | Evidence | Current symptom | Scaling risk | Suggested improvement | |---------|----------|-----------------|-------------|-----------------------| | [issue] | [path/metric] | [symptom] | [risk] | [action] |

5) Fragile/High-Churn Areas

| Area | Why fragile | Churn signal | Safe change strategy | |------|-------------|-------------|----------------------| | [path] | [reason] | [recent churn evidence] | [approach] |

6) [ASK USER] Questions

Add unresolved intent-dependent questions as a numbered list.

  1. [ASK USER] [question]

7) Evidence

  • [scan output section reference]
  • [path/to/code-file]
  • [path/to/config-or-history-evidence]

Extended Sections (Optional)

Add only when needed:

  • Full bug inventory
  • Component-level remediation roadmap
  • Cost/effort estimates by concern
  • Dependency-risk and ownership mapping