vendor-analyzer

Run exhaustive vendor codebase analysis pipeline with 5 sequential agents

Phase 3 of vendor codebase analysis. Analyzes external dependencies, internal import graphs, and checks for security vulnerabilities. <example> Context: Phase 2 structure analysis completed user: "Now analyze the dependencies" assistant: "I'll use the va-dependencies agent to analyze external and internal dependencies." <commentary> Phase 3 runs after structure analysis. Agent parses package manifests and builds dependency graphs. </commentary> </example> <example> Context: Security-focused review user: "Check what external libraries they're using and if there are vulnerabilities" assistant: "I'll use the va-dependencies agent to analyze dependencies and check for CVEs." <commentary> Security-focused dependency analysis including CVE lookup. </commentary> </example>

Phase 1 of vendor codebase analysis. Creates exhaustive file inventory with language stats, git history, and initial categorization. <example> Context: User wants to analyze a new vendor codebase user: "Analyze the serena MCP server codebase" assistant: "I'll use the va-inventory agent to create a comprehensive file inventory." <commentary> The user wants to analyze a vendor codebase. The va-inventory agent triggers first to create the foundational inventory. </commentary> </example> <example> Context: User asks for codebase statistics user: "How big is this codebase? What languages does it use?" assistant: "I'll use the va-inventory agent to scan the codebase and generate detailed statistics." <commentary> User wants language statistics and size metrics - va-inventory provides this. </commentary> </example>

Phase 2 of vendor codebase analysis. Maps architecture, module boundaries, entry points, and creates visual structure diagrams. <example> Context: Phase 1 inventory completed user: "Now map the architecture and module structure" assistant: "I'll use the va-structure agent to analyze the codebase structure." <commentary> User is requesting Phase 2 after completing Phase 1. Agent reads inventory first. </commentary> </example> <example> Context: User wants to understand code organization user: "What are the main modules and how do they relate?" assistant: "I'll use the va-structure agent to map modules and their relationships." <commentary> User asking about architectural organization - Phase 2 responsibility. </commentary> </example>

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.