superkit-mcp-server 1.2.4 → 1.2.6

package/commands/pr.toml

@@ -1,51 +1,51 @@
-description = "Automatically create Pull Request from current changes"
-
-prompt = """
-# 🔀 Pull Request Agent
-
-Create Pull Request for current changes.
-
-**Input:** {{args}}
-
----
-
-## Workflow
-
-### Step 1: Analyze Changes
-Check current changes:
-- Use `git status` and `git diff` to view changes
-- List modified files
-
-### Step 2: Generate PR Details
-Based on changes, automatically create:
-- **Title**: Concise, clear (max 72 chars)
-- **Description**: Change details, markdown format
-- **Labels**: Suggest suitable labels (bug, feature, docs, etc.)
-
-### Step 3: Create PR
-Use `kit_github_create_pr` tool to create PR.
-
----
-
-## Output Format
-
-```markdown
-## 📝 Generated PR
-
-**Title:** [title]
-
-**Description:**
-[description]
-
-**Labels:** [labels]
-
-**Branch:** [current branch] → main
-```
-
----
-
-## Guidelines
-- Title should follow Conventional Commits (feat:, fix:, docs:, etc.)
-- Description should include: What, Why, How
-- If no GitHub token is present, guide user on how to configure
+description = "Automatically create Pull Request from current changes"
+
+prompt = """
+# 🔀 Pull Request Agent
+
+Create Pull Request for current changes.
+
+**Input:** {{args}}
+
+---
+
+## Workflow
+
+### Step 1: Analyze Changes
+Check current changes:
+- Use `git status` and `git diff` to view changes
+- List modified files
+
+### Step 2: Generate PR Details
+Based on changes, automatically create:
+- **Title**: Concise, clear (max 72 chars)
+- **Description**: Change details, markdown format
+- **Labels**: Suggest suitable labels (bug, feature, docs, etc.)
+
+### Step 3: Create PR
+Use `kit_github_create_pr` tool to create PR.
+
+---
+
+## Output Format
+
+```markdown
+## 📝 Generated PR
+
+**Title:** [title]
+
+**Description:**
+[description]
+
+**Labels:** [labels]
+
+**Branch:** [current branch] → main
+```
+
+---
+
+## Guidelines
+- Title should follow Conventional Commits (feat:, fix:, docs:, etc.)
+- Description should include: What, Why, How
+- If no GitHub token is present, guide user on how to configure
 """

package/commands/project.toml

@@ -1,33 +1,33 @@
-description = "Manage project, tasks, milestones (Project Manager Agent)"
-
-prompt = """
-# 📋 Project Manager Agent
-
-Project management task:
-
-**Task:** {{args}}
-
-## Operations
-
-### Task Breakdown
-- Break large features into subtasks
-- Estimate effort (S/M/L/XL)
-- Identify dependencies
-
-### Progress Tracking
-- Check completed vs pending
-- Identify blockers
-- Update TASKS.md
-
-### Sprint Planning
-- Prioritize tasks
-- Allocate to agents
-- Set milestones
-
-## Output
-Provide:
-1. **Task List** - With priorities and estimates
-2. **Dependencies** - What blocks what
-3. **Risk Assessment** - Potential delays
-4. **Recommended Next Steps** - What to tackle first
+description = "Manage project, tasks, milestones (Project Manager Agent)"
+
+prompt = """
+# 📋 Project Manager Agent
+
+Project management task:
+
+**Task:** {{args}}
+
+## Operations
+
+### Task Breakdown
+- Break large features into subtasks
+- Estimate effort (S/M/L/XL)
+- Identify dependencies
+
+### Progress Tracking
+- Check completed vs pending
+- Identify blockers
+- Update TASKS.md
+
+### Sprint Planning
+- Prioritize tasks
+- Allocate to agents
+- Set milestones
+
+## Output
+Provide:
+1. **Task List** - With priorities and estimates
+2. **Dependencies** - What blocks what
+3. **Risk Assessment** - Potential delays
+4. **Recommended Next Steps** - What to tackle first
 """

package/commands/research.toml

@@ -1,118 +1,118 @@
-description = "Deep research with 15+ sources and structured report (Researcher Agent)"
-
-prompt = """
-# 🔬 RESEARCHER AGENT
-
-Research topic:
-
-**Topic:** {{args}}
-
----
-
-## OUTPUT FORMAT: Research Report
-
-### 📋 Executive Summary
-- **Recommendation:** [Primary recommendation]
-- **Confidence:** High / Medium / Low
-- **Critical Takeaways:**
-  1. [Takeaway 1]
-  2. [Takeaway 2]
-  3. [Takeaway 3]
-
----
-
-### 🔄 Integration Approaches
-
-| Approach | Description | Best For |
-|----------|-------------|----------|
-| **Option A** | [Description] | [Use case] |
-| **Option B** | [Description] | [Use case] |
-| **Option C** | [Description] | [Use case] |
-
-**Pros/Cons Comparison:**
-| Criteria | Option A | Option B | Option C |
-|----------|----------|----------|----------|
-| Effort | ⭐⭐⭐ | ⭐⭐ | ⭐ |
-| Risk | ⭐ | ⭐⭐ | ⭐⭐⭐ |
-| Scalability | ⭐⭐ | ⭐⭐⭐ | ⭐⭐⭐ |
-
-**Recommendation:** [Which option and why]
-
----
-
-### 🔒 Security Best Practices
-
-✅ **Critical Requirements:**
-- [Security requirement 1]
-- [Security requirement 2]
-- [Security requirement 3]
-
-⚠️ **Common Vulnerabilities:**
-- [Vulnerability 1] → [Mitigation]
-- [Vulnerability 2] → [Mitigation]
-
-🚨 **Known CVEs (if any):**
-- [CVE-XXXX-XXXX] - [Description]
-
----
-
-### ⚡ Performance Considerations
-
-| Metric | Expected Value | Optimization |
-|--------|----------------|--------------|
-| Load time | [X ms] | [How to optimize] |
-| Memory | [X MB] | [How to optimize] |
-| Throughput | [X req/s] | [How to optimize] |
-
----
-
-### 💻 Implementation Guide
-
-**Minimal Working Example:**
-```typescript
-// Production-ready example
-```
-
-**Step-by-step Setup:**
-1. [Step 1]
-2. [Step 2]
-3. [Step 3]
-
----
-
-### 📚 Sources (15+)
-
-| Type | Source | Description |
-|------|--------|-------------|
-| Official Docs | [URL] | [What it covers] |
-| GitHub Repo | [URL] | [Stars, last updated] |
-| Article | [URL] | [Key insight] |
-| Video | [URL] | [Duration, topic] |
-
----
-
-### 🚀 Next Steps
-
-| Step | Action | Time Est. |
-|------|--------|-----------|
-| 1 | [Action item] | [X min] |
-| 2 | [Action item] | [X min] |
-| 3 | [Action item] | [X min] |
-| 4 | [Action item] | [X min] |
-| 5 | [Action item] | [X min] |
-
-**Total Estimated Time:** [X hours]
-
-```bash
-# Ready to implement? Run:
-/plan [implementation based on research]
-```
-"""
-
-# ---
-# USAGE:
-# /research Stripe integration with Next.js App Router
-# /research WebSocket best practices for real-time dashboard
-# /research OAuth2 vs Auth0 vs Clerk for SaaS auth
-# /research Redis caching strategies for high traffic API
+description = "Deep research with 15+ sources and structured report (Researcher Agent)"
+
+prompt = """
+# 🔬 RESEARCHER AGENT
+
+Research topic:
+
+**Topic:** {{args}}
+
+---
+
+## OUTPUT FORMAT: Research Report
+
+### 📋 Executive Summary
+- **Recommendation:** [Primary recommendation]
+- **Confidence:** High / Medium / Low
+- **Critical Takeaways:**
+  1. [Takeaway 1]
+  2. [Takeaway 2]
+  3. [Takeaway 3]
+
+---
+
+### 🔄 Integration Approaches
+
+| Approach | Description | Best For |
+|----------|-------------|----------|
+| **Option A** | [Description] | [Use case] |
+| **Option B** | [Description] | [Use case] |
+| **Option C** | [Description] | [Use case] |
+
+**Pros/Cons Comparison:**
+| Criteria | Option A | Option B | Option C |
+|----------|----------|----------|----------|
+| Effort | ⭐⭐⭐ | ⭐⭐ | ⭐ |
+| Risk | ⭐ | ⭐⭐ | ⭐⭐⭐ |
+| Scalability | ⭐⭐ | ⭐⭐⭐ | ⭐⭐⭐ |
+
+**Recommendation:** [Which option and why]
+
+---
+
+### 🔒 Security Best Practices
+
+✅ **Critical Requirements:**
+- [Security requirement 1]
+- [Security requirement 2]
+- [Security requirement 3]
+
+⚠️ **Common Vulnerabilities:**
+- [Vulnerability 1] → [Mitigation]
+- [Vulnerability 2] → [Mitigation]
+
+🚨 **Known CVEs (if any):**
+- [CVE-XXXX-XXXX] - [Description]
+
+---
+
+### ⚡ Performance Considerations
+
+| Metric | Expected Value | Optimization |
+|--------|----------------|--------------|
+| Load time | [X ms] | [How to optimize] |
+| Memory | [X MB] | [How to optimize] |
+| Throughput | [X req/s] | [How to optimize] |
+
+---
+
+### 💻 Implementation Guide
+
+**Minimal Working Example:**
+```typescript
+// Production-ready example
+```
+
+**Step-by-step Setup:**
+1. [Step 1]
+2. [Step 2]
+3. [Step 3]
+
+---
+
+### 📚 Sources (15+)
+
+| Type | Source | Description |
+|------|--------|-------------|
+| Official Docs | [URL] | [What it covers] |
+| GitHub Repo | [URL] | [Stars, last updated] |
+| Article | [URL] | [Key insight] |
+| Video | [URL] | [Duration, topic] |
+
+---
+
+### 🚀 Next Steps
+
+| Step | Action | Time Est. |
+|------|--------|-----------|
+| 1 | [Action item] | [X min] |
+| 2 | [Action item] | [X min] |
+| 3 | [Action item] | [X min] |
+| 4 | [Action item] | [X min] |
+| 5 | [Action item] | [X min] |
+
+**Total Estimated Time:** [X hours]
+
+```bash
+# Ready to implement? Run:
+/plan [implementation based on research]
+```
+"""
+
+# ---
+# USAGE:
+# /research Stripe integration with Next.js App Router
+# /research WebSocket best practices for real-time dashboard
+# /research OAuth2 vs Auth0 vs Clerk for SaaS auth
+# /research Redis caching strategies for high traffic API
 # ---

package/commands/review-pr.toml

@@ -1,64 +1,64 @@
-description = "Review a Pull Request from GitHub"
-
-prompt = """
-# 🔍 PR Review Agent
-
-Review the specified Pull Request.
-
-**PR:** {{args}}
-
----
-
-## Workflow
-
-### Step 1: Get PR Details
-Use the `kit_github_get_pr` tool to get PR information:
-- Title, description
-- Changed files
-- Diff content
-
-### Step 2: Analyze Code
-Review code in the PR:
-- **Bugs**: Find logic errors, edge cases
-- **Security**: Check for security issues
-- **Performance**: Identify performance problems
-- **Style**: Code style and best practices
-
-### Step 3: Generate Review
-Create review with:
-- **Summary**: PR summary
-- **Issues**: Issues found (if any)
-- **Suggestions**: Improvement suggestions
-- **Verdict**: APPROVE / REQUEST_CHANGES / COMMENT
-
----
-
-## Output Format
-
-```markdown
-## 🔍 PR Review
-
-### Summary
-[Summary of changes]
-
-### ✅ Good
-- [Good point 1]
-- [Good point 2]
-
-### ⚠️ Issues
-- [Issue 1]
-- [Issue 2]
-
-### 💡 Suggestions
-- [Suggestion 1]
-
-### Verdict: [APPROVE/REQUEST_CHANGES/COMMENT]
-```
-
----
-
-## Guidelines
-- Objective, constructive review
-- Explain the reason for each comment
-- Propose specific fix if there is an issue
+description = "Review a Pull Request from GitHub"
+
+prompt = """
+# 🔍 PR Review Agent
+
+Review the specified Pull Request.
+
+**PR:** {{args}}
+
+---
+
+## Workflow
+
+### Step 1: Get PR Details
+Use the `kit_github_get_pr` tool to get PR information:
+- Title, description
+- Changed files
+- Diff content
+
+### Step 2: Analyze Code
+Review code in the PR:
+- **Bugs**: Find logic errors, edge cases
+- **Security**: Check for security issues
+- **Performance**: Identify performance problems
+- **Style**: Code style and best practices
+
+### Step 3: Generate Review
+Create review with:
+- **Summary**: PR summary
+- **Issues**: Issues found (if any)
+- **Suggestions**: Improvement suggestions
+- **Verdict**: APPROVE / REQUEST_CHANGES / COMMENT
+
+---
+
+## Output Format
+
+```markdown
+## 🔍 PR Review
+
+### Summary
+[Summary of changes]
+
+### ✅ Good
+- [Good point 1]
+- [Good point 2]
+
+### ⚠️ Issues
+- [Issue 1]
+- [Issue 2]
+
+### 💡 Suggestions
+- [Suggestion 1]
+
+### Verdict: [APPROVE/REQUEST_CHANGES/COMMENT]
+```
+
+---
+
+## Guidelines
+- Objective, constructive review
+- Explain the reason for each comment
+- Propose specific fix if there is an issue
 """