Stats
Actions
Tags
From vendor-analyzer
Use this skill when the user asks to "analyze a vendor codebase", "understand third-party code", "review vendor architecture", "document vendor dependencies", or "create codebase documentation". Triggers on mentions of vendor analysis, codebase documentation, or understanding unfamiliar/external codebases.
How this skill is triggered — by the user, by Claude, or both
Slash command
/vendor-analyzer:analyzeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when analyzing third-party/vendor codebases to understand their architecture, dependencies, and algorithms. The vendor-analyzer provides exhaustive documentation in Obsidian-compatible format.
Use this skill when analyzing third-party/vendor codebases to understand their architecture, dependencies, and algorithms. The vendor-analyzer provides exhaustive documentation in Obsidian-compatible format.
# Analyze a vendor codebase
/analyze vendors/serena
# With specific depth
/analyze vendors/serena --depth exhaustive
| Agent | Phase | Purpose |
|---|---|---|
va-inventory | 1 | File inventory, languages, git history |
va-structure | 2 | Module boundaries, entry points, exports |
va-dependencies | 3 | Dependency graph, security audit |
va-algorithms | 4 | Core logic, pseudocode, flowcharts |
va-report | 5 | Final synthesis, executive summary |
| Level | Time | Files | Use Case |
|---|---|---|---|
surface | ~30min | 10-15 | Quick overview |
standard | ~2-3h | 50-80 | Normal analysis |
deep | ~8h | 200+ | Thorough review |
exhaustive | ~24h+ | 500+ | Complete audit |
After analysis, find results in <target>/.analysis/:
.analysis/
├── 00-index.md # Main entry point
├── EXECUTIVE-SUMMARY.md # For stakeholders
├── GETTING-STARTED.md # For new developers
├── 00-structure.md # Architecture overview
├── 00-dependencies.md # Dependency summary
├── 00-algorithms.md # Algorithm index
├── _metadata/
│ └── inventory.md # File manifest
├── modules/
│ └── *.md # Module documentation
├── deps/
│ ├── internal.md # Internal dependencies
│ └── external.md # External packages
└── algorithms/
└── *.md # Algorithm documentation
Output uses Obsidian features:
[[wiki-links]] for navigation#tags for categorizationOpen .analysis/ folder as Obsidian vault for best experience.
For 50k LOC project on Opus:
npx claudepluginhub a3io/jaine-custom-marketplace --plugin vendor-analyzerDeeply explores existing codebases to map architecture, data flow, domain model, API surface, dependencies, and code health using read-only SubAgents.
Performs preliminary codebase fact-finding and produces structured research reports. Use before cw-spec to understand unfamiliar codebases and generate enriched context.
Runs a 7-phase codebase analysis using typegraph-mcp tools, producing a detailed architectural report. Useful when onboarding to an unfamiliar codebase or before making significant changes.