codebase-analyzer-mcp 1.0.0

package/commands/patterns.md

@@ -0,0 +1,75 @@
+---
+name: patterns
+description: Detect design and architecture patterns in a codebase
+user-invocable: true
+---
+
+# Find Patterns
+
+Detect design patterns, architectural patterns, and anti-patterns in a codebase.
+
+## Usage
+
+```
+/patterns [source] [options]
+```
+
+**Arguments:**
+- `source` - Local path or GitHub URL (default: current directory)
+
+**Options:**
+- `--types <patterns>` - Specific patterns to look for
+- `--anti` - Focus on anti-patterns
+
+## Available Patterns
+
+**Design Patterns:**
+- singleton, factory, observer, strategy, decorator
+- adapter, facade, repository, dependency-injection
+
+**Architectural Patterns:**
+- event-driven, pub-sub, middleware, mvc, mvvm
+- clean-architecture, hexagonal, cqrs, saga
+
+## Examples
+
+```bash
+# Find all patterns in current directory
+/patterns
+
+# Look for specific patterns
+/patterns --types singleton,factory,repository
+
+# Find anti-patterns
+/patterns --anti
+
+# Analyze GitHub repo
+/patterns https://github.com/user/repo
+```
+
+## Workflow
+
+1. **Parse arguments** from user input
+2. **Run detection** using pattern-detective agent
+3. **Present findings** with confidence levels
+4. **Map locations** for each pattern
+
+## Implementation
+
+```javascript
+const source = args.source || ".";
+const types = args.types?.split(",");
+const antiPatterns = args.anti || false;
+
+Task("pattern-detective", {
+  prompt: `Find ${antiPatterns ? "anti-patterns" : "patterns"} in ${source}${types ? ` focusing on ${types.join(", ")}` : ""}`
+});
+```
+
+## Output
+
+Returns pattern analysis with:
+- Detected patterns with confidence scores
+- File locations for each pattern
+- Anti-pattern warnings
+- Recommendations for improvement

package/commands/trace.md

@@ -0,0 +1,65 @@
+---
+name: trace
+description: Trace data flow through a codebase
+user-invocable: true
+---
+
+# Trace Dataflow
+
+Trace how data flows from an entry point through the system.
+
+## Usage
+
+```
+/trace <from> [options]
+```
+
+**Arguments:**
+- `from` - Entry point (function name, file, or description)
+
+**Options:**
+- `--to <destination>` - Trace to specific destination
+- `--source <path>` - Repository path (default: current directory)
+
+## Examples
+
+```bash
+# Trace from user login
+/trace "user login"
+
+# Trace from specific function to database
+/trace processPayment --to database
+
+# Trace API endpoint
+/trace "POST /api/users"
+
+# Trace in specific repo
+/trace checkout --source ./ecommerce-app
+```
+
+## Workflow
+
+1. **Identify entry point** from user input
+2. **Run trace** using dataflow-tracer agent
+3. **Map transformations** at each step
+4. **Identify risks** and security concerns
+
+## Implementation
+
+```javascript
+const from = args.from;
+const to = args.to;
+const source = args.source || ".";
+
+Task("dataflow-tracer", {
+  prompt: `Trace data flow from "${from}"${to ? ` to "${to}"` : ""} in ${source}`
+});
+```
+
+## Output
+
+Returns dataflow analysis with:
+- Step-by-step trace through the system
+- Data transformations at each point
+- Security observations
+- Trust boundary crossings