From code-analysis
Phase 4: Generate API reference document. Compiles the Exports/Public API sections from Phase 1 mirror documents and class hierarchy information into a public API listing with signatures and usage examples.
How this skill is triggered — by the user, by Claude, or both
Slash command
/code-analysis:api-referencesonnetThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generates `.codeanalyzer/reports/phase4/api-reference.md` by bulk-extracting public APIs via Cypher.
Generates .codeanalyzer/reports/phase4/api-reference.md by bulk-extracting public APIs via Cypher.
MATCH (c:Class)-[:DEFINES]->(m:Member)
WHERE m.visibility IN ['public','protected']
AND NOT m.attribute CONTAINS 'internal'
RETURN c.name, c.file, m.name, m.signature, m.docstring, m.visibility
ORDER BY c.name, m.visibility, m.name
For C++, also query free functions in headers:
MATCH (f:Function)
WHERE f.file =~ '.*\\.(h|hpp|hxx)$' AND f.exported = true
RETURN f.name, f.signature, f.docstring, f.file
# API Reference
## <ClassName> (<file path>)
<class-level docstring from Cypher>
### Public members
| Visibility | Signature | Notes |
### Protected members
| Visibility | Signature | Notes |
## Free functions
| Signature | File | Notes |
Notes column (1 line max per entry), using the member's mirror doc if present.api-reference.md, api-reference-2.md etc.npx claudepluginhub juyeongyi/jylee_claude_marketplace --plugin code-analysisGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.