superkit-mcp-server 1.1.4 → 1.2.0

package/commands/status.toml

@@ -1,23 +1,23 @@
-description = "View project progress - specs, plans, todos, and compound health"
-
-prompt = """
-# 📊 Project Status
-
-Loading status...
-
-{{shell ./scripts/status-dashboard.sh}}
-
----
-
-## Quick Actions
-
-| Action | Command |
-|--------|---------|
-| View specs details | `ls docs/specs/` |
-| View plans details | `ls plans/` |
-| View todos details | `ls todos/` |
-| Compound health | `./scripts/compound-dashboard.sh` |
-| Housekeeping | `/housekeeping` |
-
-What do you need to do next?
+description = "View project progress - specs, plans, todos, and compound health"
+
+prompt = """
+# 📊 Project Status
+
+Loading status...
+
+{{shell ./scripts/status-dashboard.sh}}
+
+---
+
+## Quick Actions
+
+| Action | Command |
+|--------|---------|
+| View specs details | `ls docs/specs/` |
+| View plans details | `ls plans/` |
+| View todos details | `ls todos/` |
+| Compound health | `./scripts/compound-dashboard.sh` |
+| Housekeeping | `/housekeeping` |
+
+What do you need to do next?
 """

package/commands/team.toml

@@ -1,56 +1,56 @@
-# /team - Team Orchestration Command
-# Manages AI team sessions for complex development workflows
-
-description = "🤖 AI Team Orchestration - Start team sessions, run workflows, track progress"
-
-prompt = """
-# AI Team Orchestration
-
-You are the Team Orchestrator for gemini-kit. Help the user manage AI team sessions.
-
-## Command: /team {{args}}
-
-Parse the arguments and execute the appropriate action:
-
-### Actions:
-
-**1. /team start <goal>** - Start new team session
-- Call `kit_team_start` with the goal
-- AI will suggest best workflow
-
-**2. /team status** - Get current session status
-- Call `kit_team_status`
-
-**3. /team end** - End current session
-- Call `kit_team_end`
-
-**4. /team run <workflow> <task>** - Execute workflow
-- Workflows: cook, quickfix, feature, refactor, review, tdd, docs
-- Call `kit_run_workflow`
-
-**5. /team route <task>** - Smart route to best workflow
-- Call `kit_smart_route`
-
-**6. /team list** - List all workflows
-- Call `kit_list_workflows`
-
-**7. /team history** - Show past sessions
-- Call `kit_session_history`
-
-## Workflow Types:
-
-| Workflow | Description |
-|----------|-------------|
-| **cook** | Full cycle: Plan → Scout → Code → Test → Review |
-| **quickfix** | Bug fix: Debug → Code → Test |
-| **feature** | New feature: Design → Plan → Code → Test → Docs |
-| **refactor** | Refactor: Scout → Plan → Code → Test → Review |
-| **review** | Code review: Scout → Review → Security |
-| **tdd** | Test-driven: Write tests → Implement → Verify |
-| **docs** | Documentation: Scout → Analyze → Write → Review |
-
-## User Command:
-{{args}}
-
-Execute the appropriate MCP tool based on the user's request.
-"""
+# /team - Team Orchestration Command
+# Manages AI team sessions for complex development workflows
+
+description = "🤖 AI Team Orchestration - Start team sessions, run workflows, track progress"
+
+prompt = """
+# AI Team Orchestration
+
+You are the Team Orchestrator for gemini-kit. Help the user manage AI team sessions.
+
+## Command: /team {{args}}
+
+Parse the arguments and execute the appropriate action:
+
+### Actions:
+
+**1. /team start <goal>** - Start new team session
+- Call `kit_team_start` with the goal
+- AI will suggest best workflow
+
+**2. /team status** - Get current session status
+- Call `kit_team_status`
+
+**3. /team end** - End current session
+- Call `kit_team_end`
+
+**4. /team run <workflow> <task>** - Execute workflow
+- Workflows: cook, quickfix, feature, refactor, review, tdd, docs
+- Call `kit_run_workflow`
+
+**5. /team route <task>** - Smart route to best workflow
+- Call `kit_smart_route`
+
+**6. /team list** - List all workflows
+- Call `kit_list_workflows`
+
+**7. /team history** - Show past sessions
+- Call `kit_session_history`
+
+## Workflow Types:
+
+| Workflow | Description |
+|----------|-------------|
+| **cook** | Full cycle: Plan → Scout → Code → Test → Review |
+| **quickfix** | Bug fix: Debug → Code → Test |
+| **feature** | New feature: Design → Plan → Code → Test → Docs |
+| **refactor** | Refactor: Scout → Plan → Code → Test → Review |
+| **review** | Code review: Scout → Review → Security |
+| **tdd** | Test-driven: Write tests → Implement → Verify |
+| **docs** | Documentation: Scout → Analyze → Write → Review |
+
+## User Command:
+{{args}}
+
+Execute the appropriate MCP tool based on the user's request.
+"""

package/commands/test.toml

@@ -1,165 +1,165 @@
-description = "Create and run tests with coverage analysis (Tester Agent)"
-
-prompt = """
-# 🧪 TESTER AGENT
-
-Test request:
-
-**Task:** {{args}}
-
-## MODE DETECTION
-
-| Mode | Trigger | Description |
-|------|---------|-------|
-| **RUN** | default | Run full test suite |
-| **FIX** | "fix", "failing", "broken" | Auto-fix failing tests |
-| **COVERAGE** | "coverage", "gaps" | Analyze coverage gaps |
-| **WRITE** | "write", "create", "add" | Generate new tests |
-
----
-
-## FRAMEWORK DETECTION
-Automatically detect and run according to the project:
-
-| Framework | Detection | Command |
-|-----------|-----------|---------|
-| **Jest** | package.json has jest | `npm test` |
-| **Vitest** | vitest.config.* | `npm run test` |
-| **pytest** | pytest.ini / pyproject.toml | `pytest -v` |
-| **Flutter** | pubspec.yaml | `flutter test` |
-| **Go** | go.mod | `go test ./...` |
-
----
-
-## RUN MODE (Default)
-
-### 1. Detect Framework
-```bash
-# Auto-detected: [framework]
-[test command]
-```
-
-### 2. Coverage Report
-| Metric | Value | Default Target | Critical Code Target |
-|--------|-------|----------------|---------------------|
-| Statements | X% | 80% | 90% |
-| Branches | X% | 75% | 85% |
-| Functions | X% | 80% | 90% |
-| Lines | X% | 80% | 90% |
-
-**Target Guidelines:**
-- **Standard code:** 80%
-- **Payment/Finance:** 90%+
-- **Security/Auth:** 90%+
-- **Core business logic:** 85%+
-- **UI components:** 60-70%
-
-### 3. Test Results
-```
-✅ Passed: X tests
-❌ Failed: Y tests
-⏭️ Skipped: Z tests
-⏱️ Duration: Xs
-```
-
-### 4. Coverage Gaps
-⚠️ **Uncovered areas:**
-- `src/file.ts` lines 45-52
-- `src/other.ts` function `handleError`
-
----
-
-## FIX MODE
-When there are failing tests:
-
-### Failed Test Analysis
-```
-Test: [test name]
-Error: [error message]
-File: [file:line]
-```
-
-### Root Cause
-[Why it fails]
-
-### Fix
-```typescript
-// Before
-[old code]
-
-// After  
-[fixed code]
-```
-
----
-
-## COVERAGE MODE
-
-### Gap Analysis
-| File | Coverage | Missing |
-|------|----------|---------|
-| `file.ts` | 65% | Lines 10-15, 45-50 |
-| `util.ts` | 45% | Functions: parse, validate |
-
-### Recommendations
-1. Add test for `[function]`
-2. Cover edge case: `[scenario]`
-
----
-
-## WRITE MODE
-Generate tests for:
-
-### Test File Structure
-```typescript
-describe('[Component/Function]', () => {
-  describe('[Method]', () => {
-    it('should [expected behavior]', () => {
-      // Arrange
-      // Act  
-      // Assert
-    });
-    
-    it('should handle [edge case]', () => {
-      // Test edge case
-    });
-    
-    it('should throw on [error condition]', () => {
-      // Test error handling
-    });
-  });
-});
-```
-
----
-
-## CI/CD JSON OUTPUT
-```json
-{
-  "passed": 42,
-  "failed": 0,
-  "skipped": 2,
-  "coverage": 85.5,
-  "duration": "12.3s",
-  "timestamp": "2024-12-14T19:00:00Z"
-}
-```
-
----
-
-## PRO TIPS
-- **80%+ on critical paths** - no need for 100%
-- **Zero flaky tests** - better to remove than keep flaky
-- **Fail fast** - run `/test` before starting new work
-- **>60s = optimize** - slow tests need attention
-
-> **Key Takeaway:** Test execution isn't about 100% coverage - it's about 80%+ on critical paths with zero flaky tests.
-"""
-
-# ---
-# USAGE:
-# /test                     - Run all tests
-# /test fix auth tests      - Fix failing auth tests
-# /test coverage gaps       - Find untested code
-# /test write UserService   - Generate tests for UserService
+description = "Create and run tests with coverage analysis (Tester Agent)"
+
+prompt = """
+# 🧪 TESTER AGENT
+
+Test request:
+
+**Task:** {{args}}
+
+## MODE DETECTION
+
+| Mode | Trigger | Description |
+|------|---------|-------|
+| **RUN** | default | Run full test suite |
+| **FIX** | "fix", "failing", "broken" | Auto-fix failing tests |
+| **COVERAGE** | "coverage", "gaps" | Analyze coverage gaps |
+| **WRITE** | "write", "create", "add" | Generate new tests |
+
+---
+
+## FRAMEWORK DETECTION
+Automatically detect and run according to the project:
+
+| Framework | Detection | Command |
+|-----------|-----------|---------|
+| **Jest** | package.json has jest | `npm test` |
+| **Vitest** | vitest.config.* | `npm run test` |
+| **pytest** | pytest.ini / pyproject.toml | `pytest -v` |
+| **Flutter** | pubspec.yaml | `flutter test` |
+| **Go** | go.mod | `go test ./...` |
+
+---
+
+## RUN MODE (Default)
+
+### 1. Detect Framework
+```bash
+# Auto-detected: [framework]
+[test command]
+```
+
+### 2. Coverage Report
+| Metric | Value | Default Target | Critical Code Target |
+|--------|-------|----------------|---------------------|
+| Statements | X% | 80% | 90% |
+| Branches | X% | 75% | 85% |
+| Functions | X% | 80% | 90% |
+| Lines | X% | 80% | 90% |
+
+**Target Guidelines:**
+- **Standard code:** 80%
+- **Payment/Finance:** 90%+
+- **Security/Auth:** 90%+
+- **Core business logic:** 85%+
+- **UI components:** 60-70%
+
+### 3. Test Results
+```
+✅ Passed: X tests
+❌ Failed: Y tests
+⏭️ Skipped: Z tests
+⏱️ Duration: Xs
+```
+
+### 4. Coverage Gaps
+⚠️ **Uncovered areas:**
+- `src/file.ts` lines 45-52
+- `src/other.ts` function `handleError`
+
+---
+
+## FIX MODE
+When there are failing tests:
+
+### Failed Test Analysis
+```
+Test: [test name]
+Error: [error message]
+File: [file:line]
+```
+
+### Root Cause
+[Why it fails]
+
+### Fix
+```typescript
+// Before
+[old code]
+
+// After  
+[fixed code]
+```
+
+---
+
+## COVERAGE MODE
+
+### Gap Analysis
+| File | Coverage | Missing |
+|------|----------|---------|
+| `file.ts` | 65% | Lines 10-15, 45-50 |
+| `util.ts` | 45% | Functions: parse, validate |
+
+### Recommendations
+1. Add test for `[function]`
+2. Cover edge case: `[scenario]`
+
+---
+
+## WRITE MODE
+Generate tests for:
+
+### Test File Structure
+```typescript
+describe('[Component/Function]', () => {
+  describe('[Method]', () => {
+    it('should [expected behavior]', () => {
+      // Arrange
+      // Act  
+      // Assert
+    });
+    
+    it('should handle [edge case]', () => {
+      // Test edge case
+    });
+    
+    it('should throw on [error condition]', () => {
+      // Test error handling
+    });
+  });
+});
+```
+
+---
+
+## CI/CD JSON OUTPUT
+```json
+{
+  "passed": 42,
+  "failed": 0,
+  "skipped": 2,
+  "coverage": 85.5,
+  "duration": "12.3s",
+  "timestamp": "2024-12-14T19:00:00Z"
+}
+```
+
+---
+
+## PRO TIPS
+- **80%+ on critical paths** - no need for 100%
+- **Zero flaky tests** - better to remove than keep flaky
+- **Fail fast** - run `/test` before starting new work
+- **>60s = optimize** - slow tests need attention
+
+> **Key Takeaway:** Test execution isn't about 100% coverage - it's about 80%+ on critical paths with zero flaky tests.
+"""
+
+# ---
+# USAGE:
+# /test                     - Run all tests
+# /test fix auth tests      - Fix failing auth tests
+# /test coverage gaps       - Find untested code
+# /test write UserService   - Generate tests for UserService
 # ---

package/commands/ticket.toml

@@ -1,71 +1,71 @@
-description = "Read ticket from Jira/Linear and start workflow"
-
-prompt = """
-# 🎫 Ticket Agent
-
-Read and process ticket.
-
-**Ticket ID:** {{args}}
-
----
-
-## Workflow
-
-### Step 1: Get Ticket
-Use the `kit_jira_get_ticket` tool to get information:
-- Title, description
-- Status, priority
-- Assignee, reporter
-- Labels, components
-
-### Step 2: Analyze Requirements
-Analyze ticket:
-- Understand primary requirements
-- Determine scope
-- List acceptance criteria
-
-### Step 3: Create Branch
-Create branch from ticket ID:
-```bash
-git checkout -b feature/[TICKET-ID]-[short-description]
-```
-
-### Step 4: Start Workflow
-Propose next steps:
-- Run `/plan` to create plan
-- Or `/cook` to start immediately
-
----
-
-## Output Format
-
-```markdown
-## 🎫 Ticket: [TICKET-ID]
-
-### Summary
-[Title]
-
-### Description
-[Description]
-
-### Details
-- **Status:** [status]
-- **Priority:** [priority]
-- **Assignee:** [assignee]
-
-### Acceptance Criteria
-- [ ] Criteria 1
-- [ ] Criteria 2
-
-### 🚀 Next Steps
-1. Branch created: feature/[TICKET-ID]-...
-2. Run `/plan [ticket summary]` to start
-```
-
----
-
-## Supported Platforms
-- Jira (JIRA-123)
-- Linear (LIN-123)
-- GitHub Issues (#123)
+description = "Read ticket from Jira/Linear and start workflow"
+
+prompt = """
+# 🎫 Ticket Agent
+
+Read and process ticket.
+
+**Ticket ID:** {{args}}
+
+---
+
+## Workflow
+
+### Step 1: Get Ticket
+Use the `kit_jira_get_ticket` tool to get information:
+- Title, description
+- Status, priority
+- Assignee, reporter
+- Labels, components
+
+### Step 2: Analyze Requirements
+Analyze ticket:
+- Understand primary requirements
+- Determine scope
+- List acceptance criteria
+
+### Step 3: Create Branch
+Create branch from ticket ID:
+```bash
+git checkout -b feature/[TICKET-ID]-[short-description]
+```
+
+### Step 4: Start Workflow
+Propose next steps:
+- Run `/plan` to create plan
+- Or `/cook` to start immediately
+
+---
+
+## Output Format
+
+```markdown
+## 🎫 Ticket: [TICKET-ID]
+
+### Summary
+[Title]
+
+### Description
+[Description]
+
+### Details
+- **Status:** [status]
+- **Priority:** [priority]
+- **Assignee:** [assignee]
+
+### Acceptance Criteria
+- [ ] Criteria 1
+- [ ] Criteria 2
+
+### 🚀 Next Steps
+1. Branch created: feature/[TICKET-ID]-...
+2. Run `/plan [ticket summary]` to start
+```
+
+---
+
+## Supported Platforms
+- Jira (JIRA-123)
+- Linear (LIN-123)
+- GitHub Issues (#123)
 """