Capture Knowledge
Description
--- description: Document a code entry point in knowledge docs. --- Guide me through creating a structured understanding of a code entry point and saving it to the knowledge docs. 1. **Gather & Validate Entry Point** — If not already provided, ask for: entry point (file, folder, function, API), why it matters (feature, bug, investigation), and desired depth or focus areas. Confirm the entry point exists; if ambiguous or not found, clarify or suggest alternatives. 2. **Use Memory for Context**
Installation
Installs to ~/.claude/commands/codeaholicguy-ai-devkit-capture-knowledge.md
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/codeaholicguy/ai-devkit/HEAD/.claude/commands/capture-knowledge.md -o ~/.claude/commands/codeaholicguy-ai-devkit-capture-knowledge.md Restart Claude Code, or start a new session, for it to be picked up.
Full documentation available on GitHub
View Source RepositoryRelated Skills
Auto Update
Pull the latest ECC repo changes and reinstall the current managed targets.
Ecc Guide
Navigate ECC's current agents, skills, commands, hooks, install profiles, and docs from the live repository su
Epic Claim
Claim an epic issue, stamp coordination state, and sync local ownership.
Epic Publish
Publish a validated epic update back to the issue and local cache.
Epic Review
Mark epic review requested, approved, or changes requested.
Epic Unblock
Sweep blocked epic issues and reopen anything whose dependencies are closed.