codebase-analyzer-mcp 2.0.5 → 2.1.1

package/.claude-plugin/marketplace.json

@@ -6,13 +6,13 @@
   },
   "metadata": {
     "description": "Multi-layer codebase analysis tools",
-    "version": "2.0.5"
+    "version": "2.1.1"
   },
   "plugins": [
     {
       "name": "codebase-analyzer",
-      "description": "Multi-layer codebase analysis with Gemini AI. 4 agents, 5 commands, 3 skills for architecture analysis, pattern detection, and dataflow tracing.",
-      "version": "2.0.5",
+      "description": "Multi-layer codebase analysis with Gemini AI. 4 agents, 1 command, 1 skill for architecture analysis, pattern detection, and dataflow tracing.",
+      "version": "2.1.1",
       "author": {
         "name": "Jake Correa",
         "url": "https://github.com/jaykaycodes"

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "codebase-analyzer",
-  "version": "2.0.5",
-  "description": "Multi-layer codebase analysis with Gemini AI. 4 agents, 5 commands, 3 skills for architecture analysis, pattern detection, and dataflow tracing.",
+  "version": "2.1.1",
+  "description": "Multi-layer codebase analysis with Gemini AI. 4 agents, 1 command, 1 skill for architecture analysis, pattern detection, and dataflow tracing.",
   "author": {
     "name": "Jake Correa",
     "url": "https://github.com/jaykaycodes"

package/CLAUDE.md

@@ -23,8 +23,8 @@ pnpm install && pnpm build
 | Component | Count | Purpose |
 |-----------|-------|---------|
 | Agents | 4 | Specialized analysis tasks |
-| Commands | 5 | User-invocable actions |
-| Skills | 3 | Context-loaded guidance |
+| Commands | 1 | User-invocable actions |
+| Skills | 1 | Context-loaded guidance |
 | MCP Server | 1 | Tool interface for Claude |
 
 ### Agents
@@ -40,19 +40,13 @@ pnpm install && pnpm build
 
 | Command | Usage |
 |---------|-------|
-| `/analyze` | Analyze a codebase |
-| `/patterns` | Find design patterns |
-| `/trace` | Trace data flow |
-| `/explore` | Quick exploration |
-| `/compare` | Compare repositories |
+| `/cba:analyze` | Analyze a codebase |
 
 ### Skills
 
 | Skill | Purpose |
 |-------|---------|
-| `codebase-analysis` | How to use the MCP tools |
-| `add-mcp-tool` | Guide for adding new tools |
-| `debugging-analysis` | Troubleshooting analysis issues |
+| `cba:codebase-analysis` | How to use the MCP tools |
 
 ## Architecture
 
@@ -77,7 +71,9 @@ See [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) for system design.
 | Tool | Purpose | Cost |
 |------|---------|------|
 | `analyze_repo` | Full analysis with expandable sections | Varies |
+| `query_repo` | Ask questions about a codebase | Medium |
 | `expand_section` | Drill into specific sections | Low |
+| `read_files` | Read source files from cached analysis | None |
 | `find_patterns` | Pattern detection | Medium |
 | `trace_dataflow` | Data flow tracing | Medium |
 | `get_analysis_capabilities` | List capabilities | None |

package/README.md

@@ -13,7 +13,7 @@ Analyze any codebase with Gemini AI. Progressive disclosure keeps costs low - st
 claude /plugin install https://github.com/jaykaycodes/codebase-analyzer-mcp
 ```
 
-Then use `/analyze`, `/patterns`, `/trace`, or `/explore` commands.
+Then use `/cba:analyze` to analyze a codebase, or just ask questions naturally.
 
 ### MCP Server
 
@@ -30,7 +30,7 @@ Add to `~/.mcp.json` (create if it doesn't exist):
 }
 ```
 
-Restart Claude Code, then use the `analyze_repo`, `find_patterns`, or `trace_dataflow` tools.
+Restart Claude Code, then use the `analyze_repo` or `query_repo` tools.
 
 **Optional:** For semantic analysis with Gemini AI, get an API key at https://aistudio.google.com/apikey and add it:
 
@@ -51,11 +51,12 @@ Restart Claude Code, then use the `analyze_repo`, `find_patterns`, or `trace_dat
 ### CLI
 
 ```bash
-npx codebase-analyzer-mcp analyze .                    # Standard analysis
-npx codebase-analyzer-mcp analyze . -d surface         # Fast, free overview
-npx codebase-analyzer-mcp analyze . -d deep -s         # Full semantic analysis
-npx codebase-analyzer-mcp patterns .                   # Find design patterns
-npx codebase-analyzer-mcp dataflow . "user login"      # Trace data flow
+npx codebase-analyzer-mcp analyze .                              # Standard analysis
+npx codebase-analyzer-mcp analyze . -d surface                   # Fast, free overview
+npx codebase-analyzer-mcp analyze . -d deep -s                   # Full semantic analysis
+npx codebase-analyzer-mcp query . "how is auth handled?"         # Ask a question
+npx codebase-analyzer-mcp patterns .                             # Find design patterns
+npx codebase-analyzer-mcp dataflow . "user login"                # Trace data flow
 ```
 
 ## What It Does
@@ -73,19 +74,31 @@ Analysis results include expandable sections - you only pay for what you drill i
 | Tool | Description |
 |------|-------------|
 | `analyze_repo` | Full analysis with progressive disclosure |
+| `query_repo` | Ask questions about a codebase |
 | `expand_section` | Drill into specific sections |
+| `read_files` | Read source files from a cached analysis |
 | `find_patterns` | Detect design/architecture patterns |
 | `trace_dataflow` | Trace data flow through the system |
+| `get_analysis_capabilities` | List supported languages and analysis options |
 
-## Plugin Commands & Agents
+## Plugin
 
-| Command | Agent | Purpose |
-|---------|-------|---------|
-| `/analyze` | `architecture-analyzer` | Full architecture analysis |
-| `/patterns` | `pattern-detective` | Find design patterns |
-| `/trace` | `dataflow-tracer` | Trace data flow |
-| `/explore` | `codebase-explorer` | Quick exploration |
-| `/compare` | - | Compare repositories |
+### Command
+
+```
+/cba:analyze [source] [--depth surface|standard|deep] [--focus <paths>]
+```
+
+### Agents
+
+| Agent | Purpose |
+|-------|---------|
+| `architecture-analyzer` | Full codebase architecture analysis |
+| `pattern-detective` | Design/anti-pattern detection |
+| `dataflow-tracer` | Data flow tracing through systems |
+| `codebase-explorer` | Quick exploration and Q&A |
+
+Agents are routed automatically based on your question — just ask naturally.
 
 ---
 
@@ -105,7 +118,7 @@ git clone https://github.com/jaykaycodes/codebase-analyzer-mcp.git
 cd codebase-analyzer-mcp
 bun install
 bun run dev           # Watch mode
-bun run build:js      # Build JS
+bun run build         # Build
 bun run cba analyze . # Test CLI
 ```
 

package/agents/analysis/architecture-analyzer.md

@@ -1,5 +1,5 @@
 ---
-name: architecture-analyzer
+name: cba:architecture-analyzer
 description: "Use this agent when you need to understand a codebase's architecture, identify patterns, and get a high-level overview. This agent uses the codebase-analyzer MCP to perform multi-layer analysis with progressive disclosure - starting cheap and drilling down as needed.\n\n<example>Context: User wants to understand a new codebase.\nuser: \"Help me understand the architecture of this repo\"\nassistant: \"I'll use the architecture-analyzer agent to analyze the codebase structure and patterns.\"\n<commentary>Since the user wants architectural understanding, use architecture-analyzer to run progressive analysis.</commentary></example>\n\n<example>Context: User is evaluating a library.\nuser: \"What patterns does this library use?\"\nassistant: \"Let me use the architecture-analyzer agent to detect patterns in this codebase.\"\n<commentary>Pattern detection is a core capability of architecture-analyzer.</commentary></example>"
 model: haiku
 ---

package/agents/analysis/dataflow-tracer.md

@@ -1,5 +1,5 @@
 ---
-name: dataflow-tracer
+name: cba:dataflow-tracer
 description: "Use this agent when you need to understand how data flows through a system - from entry points through transformations to outputs. Essential for debugging, security analysis, and understanding complex systems.\n\n<example>Context: User debugging data issue.\nuser: \"How does user input flow through the checkout process?\"\nassistant: \"I'll use the dataflow-tracer agent to trace the data path.\"\n<commentary>Tracing data from entry point through system is dataflow-tracer's specialty.</commentary></example>\n\n<example>Context: Security review.\nuser: \"Where does this API input go? I want to check for injection risks.\"\nassistant: \"Let me trace the dataflow from that API endpoint.\"\n<commentary>Security-focused dataflow tracing.</commentary></example>"
 model: haiku
 ---

package/agents/analysis/pattern-detective.md

@@ -1,5 +1,5 @@
 ---
-name: pattern-detective
+name: cba:pattern-detective
 description: "Use this agent when you need to find specific design patterns, anti-patterns, or architectural patterns in a codebase. Specializes in pattern detection with confidence levels and location mapping.\n\n<example>Context: User suspects anti-patterns in code.\nuser: \"Are there any anti-patterns in this codebase?\"\nassistant: \"I'll use the pattern-detective agent to scan for anti-patterns.\"\n<commentary>Pattern detection with focus on anti-patterns is pattern-detective's specialty.</commentary></example>\n\n<example>Context: User wants to understand design decisions.\nuser: \"What design patterns are used in this authentication system?\"\nassistant: \"Let me use the pattern-detective agent to analyze patterns in the auth code.\"\n<commentary>Focused pattern analysis with area filtering.</commentary></example>"
 model: haiku
 ---

package/agents/research/codebase-explorer.md

@@ -1,5 +1,5 @@
 ---
-name: codebase-explorer
+name: cba:codebase-explorer
 description: "Use this agent for open-ended codebase exploration - understanding structure, finding relevant files, and answering questions about how things work. Lighter weight than full architecture analysis.\n\n<example>Context: User exploring new codebase.\nuser: \"What's in this repo?\"\nassistant: \"I'll use the codebase-explorer agent to give you a quick overview.\"\n<commentary>Quick exploration, not deep analysis.</commentary></example>\n\n<example>Context: User looking for specific functionality.\nuser: \"Where is the email sending logic?\"\nassistant: \"Let me explore the codebase to find email-related code.\"\n<commentary>Targeted exploration for specific functionality.</commentary></example>"
 model: haiku
 ---
@@ -24,10 +24,9 @@ Extract:
 
 ### Targeted Search
 
-For "where is X?" questions:
+For "where is X?" or "how does X work?" questions:
 
-1. **Surface scan** to understand structure
-2. **Query the repo** for specific questions:
+1. **Query the repo** for AI-powered answers:
 
 ```
 mcp__codebase-analyzer__query_repo(
@@ -36,14 +35,21 @@ mcp__codebase-analyzer__query_repo(
 )
 ```
 
-### Comparison
+2. **Read relevant files** using the analysisId from the response:
 
-For "how does this compare to Y?":
+```
+mcp__codebase-analyzer__read_files(
+  analysisId: "<from query_repo result>",
+  paths: ["src/services/email.ts", "src/templates/"]
+)
+```
+
+3. **Expand sections** for deeper module understanding:
 
 ```
-mcp__codebase-analyzer__compare_repos(
-  sources: ["<path1>", "<path2>"],
-  aspect: "authentication"
+mcp__codebase-analyzer__expand_section(
+  analysisId: "<from query_repo result>",
+  sectionId: "module_src_services"
 )
 ```
 
@@ -95,7 +101,9 @@ mcp__codebase-analyzer__compare_repos(
 ## Guidelines
 
 **DO:**
-- Start with surface analysis (fast, cheap)
+- Start with `query_repo` for targeted questions (fast, reuses cache)
+- Use `analyze_repo` with surface depth for overviews
+- Follow up with `read_files` to examine specific code
 - Give actionable summaries, not data dumps
 - Point to specific files and line numbers
 - Suggest what to explore next

package/commands/analyze.md

@@ -1,5 +1,5 @@
 ---
-name: analyze
+name: cba:analyze
 description: Analyze a codebase with progressive disclosure
 user-invocable: true
 ---
@@ -11,7 +11,7 @@ Analyze a repository using multi-layer progressive disclosure.
 ## Usage
 
 ```
-/analyze [source] [options]
+/cba:analyze [source] [options]
 ```
 
 **Arguments:**
@@ -26,19 +26,19 @@ Analyze a repository using multi-layer progressive disclosure.
 
 ```bash
 # Analyze current directory
-/analyze
+/cba:analyze
 
 # Analyze with surface depth (fast)
-/analyze --depth surface
+/cba:analyze --depth surface
 
 # Analyze specific GitHub repo
-/analyze https://github.com/user/repo
+/cba:analyze https://github.com/user/repo
 
 # Focus on specific module
-/analyze --focus src/api
+/cba:analyze --focus src/api
 
 # Deep analysis with semantics
-/analyze --depth deep --semantics
+/cba:analyze --depth deep --semantics
 ```
 
 ## Workflow
@@ -58,7 +58,7 @@ const focus = args.focus;
 const semantics = args.semantics || false;
 
 // Use architecture-analyzer agent
-Task("architecture-analyzer", {
+Task("cba:architecture-analyzer", {
   prompt: `Analyze ${source} at ${depth} depth${focus ? `, focusing on ${focus}` : ""}${semantics ? " with semantic analysis" : ""}`
 });
 ```