From ai-devkit
Captures structured knowledge about code entry points like modules, files, folders, functions, or APIs, analyzes dependencies, and saves docs with mermaid diagrams. Use to document or map code.
npx claudepluginhub codeaholicguy/ai-devkitThis skill uses the workspace's default tool permissions.
Build structured understanding of code entry points with an analysis-first workflow.
Explains specific files, functions, or modules in depth using knowledge graph nodes, edges, layers, and source code analysis.
Generates C4 code-level documentation for code directories including function signatures, arguments, dependencies, structure, and Mermaid diagrams for OOP or functional code. Use for individual modules.
Creates or updates .meridian/docs/ knowledge files for modules or directories. Generates concise reference docs with frontmatter summaries and read_when keywords for agent context routing.
Share bugs, ideas, or general feedback.
Build structured understanding of code entry points with an analysis-first workflow.
npx ai-devkit@latest memory search --query "<entry point name or purpose>"calculateTotalPrice → calculate-total-price).docs/ai/implementation/knowledge-{name}.md using the Output Template.| Rationalization | Why It's Wrong | Do Instead |
|---|---|---|
| "I already understand this code" | Understanding ≠ documented understanding | Write it down, then verify |
| "The code is self-documenting" | Future readers lack your current context | Capture the why, not just the what |
| "Dependencies are obvious" | Implicit dependencies cause surprises | Map them explicitly to depth 3 |