superkit-mcp-server 1.2.4 → 1.2.6

package/skills/workflows/reproduce-bug.md

@@ -1,118 +1,118 @@
----
-description: Reproduce reported bugs systematically. Use when investigating bug reports.
----
-
-# /reproduce-bug - Systematic Bug Reproduction
-
-Attempt to reproduce a reported bug following the steps provided.
-
-## Workflow
-
-### Step 0: Establish Context (MANDATORY)
-
-> [!IMPORTANT]
-> If you are starting a new session to reproduce this bug, you MUST establish context first.
-
-**Run the context resumer:**
-
-```bash
-// turbo
-Call MCP `call_tool_logger_manager` { action: "logWorkflow", name: "/reproduce-bug", outcome: "success" }
-Call MCP `call_tool_compound_manager` { action: "search", terms: [ "bug reproduction"] }
-```
-
-**Action:** Follow `skills/session-resume/SKILL.md` to ensure all previous context and state are restored.
-
----
-
-### Step 1: Setup Environment
-
-Match the reported environment as closely as possible.
-
-### Step 2: Follow Reproduction Steps
-
-Execute each step exactly as documented.
-
-### Step 3: Document Results
-
-```markdown
-## Reproduction Attempt
-
-**Bug Report:** #{issue_number}
-**Date:** {date}
-**Environment:** {your environment}
-
-### Steps Followed
-1. ✅ Step 1 - {result}
-2. ✅ Step 2 - {result}
-3. ❌/✅ Step 3 - {result}
-
-### Result
-- [ ] **Reproduced:** Yes/No
-- [ ] **Consistent:** Every time / Intermittent / Once
-
-### Additional Observations
-{Any patterns noticed}
-
-### Next Steps
-- [ ] Debug further
-- [ ] Request more info
-- [ ] Plan fix with /plan
-```
-
----
-
-### Step 4: Persist Next Steps (MANDATORY)
-
-> [!IMPORTANT]
-> **Do not skip.** Reproduction results are lost if not converted to todos.
-
-**If reproduced:**
-**If reproduced:**
-```bash
-# Create todo to fix the bug
-Call MCP `call_tool_todo_manager` { action: "create", priority: "p1", title: "Fix: {Bug Title}", description: "TODO description" }
-  "Reproduction successful for issue #{issue_number}.\n\nReproduction Details:\n(Link to reproduction steps and results)" \
-  "Fix the bug" \
-  "Verify fix with reproduction steps"
-```
-
-**If NOT reproduced / Need info:**
-```bash
-# Create todo to follow up
-Call MCP `call_tool_todo_manager` { action: "create", priority: "p2", title: "Follow Up: Issue #{issue_number}", description: "TODO description" }
-  "Could not reproduce or need more info for issue #{issue_number}." \
-  "Request more information" \
-  "Attempt reproduction on different environment"
-```
-
-### Phase 5: Completion & Handoff
-
-#### Step 1: Establish Terminal UI State
-
-```javascript
-await task_boundary({
-  TaskName: "[COMPLETED] Reproduce Bug",
-  TaskStatus: "Reproduction attempt recorded. Offering next steps.",
-  Mode: "VERIFICATION",
-  TaskSummary: "Reproduction attempt for #{issue}. Result: {Reproduced/Not Reproduced}. Next steps persisted in todo."
-});
-```
-
-#### Step 2: Mandatory Handoff
-
-```bash
-✓ Reproduction attempt complete
-
-Next steps:
-1. /plan - Plan the fix (if reproduced)
-2. /report-bug - If new bug discovered during attempts
-3. /housekeeping - Cleanup context
-```
-
----
-
-## References
-
-- Report bugs: `/report-bug`
-- Plan fix: `/plan`
+---
+description: Reproduce reported bugs systematically. Use when investigating bug reports.
+---
+
+# /reproduce-bug - Systematic Bug Reproduction
+
+Attempt to reproduce a reported bug following the steps provided.
+
+## Workflow
+
+### Step 0: Establish Context (MANDATORY)
+
+> [!IMPORTANT]
+> If you are starting a new session to reproduce this bug, you MUST establish context first.
+
+**Run the context resumer:**
+
+```bash
+// turbo
+Call MCP `call_tool_logger_manager` { action: "logWorkflow", name: "/reproduce-bug", outcome: "success" }
+Call MCP `call_tool_compound_manager` { action: "search", terms: [ "bug reproduction"] }
+```
+
+**Action:** Follow `skills/session-resume/SKILL.md` to ensure all previous context and state are restored.
+
+---
+
+### Step 1: Setup Environment
+
+Match the reported environment as closely as possible.
+
+### Step 2: Follow Reproduction Steps
+
+Execute each step exactly as documented.
+
+### Step 3: Document Results
+
+```markdown
+## Reproduction Attempt
+
+**Bug Report:** #{issue_number}
+**Date:** {date}
+**Environment:** {your environment}
+
+### Steps Followed
+1. ✅ Step 1 - {result}
+2. ✅ Step 2 - {result}
+3. ❌/✅ Step 3 - {result}
+
+### Result
+- [ ] **Reproduced:** Yes/No
+- [ ] **Consistent:** Every time / Intermittent / Once
+
+### Additional Observations
+{Any patterns noticed}
+
+### Next Steps
+- [ ] Debug further
+- [ ] Request more info
+- [ ] Plan fix with /plan
+```
+
+---
+
+### Step 4: Persist Next Steps (MANDATORY)
+
+> [!IMPORTANT]
+> **Do not skip.** Reproduction results are lost if not converted to todos.
+
+**If reproduced:**
+**If reproduced:**
+```bash
+# Create todo to fix the bug
+Call MCP `call_tool_todo_manager` { action: "create", priority: "p1", title: "Fix: {Bug Title}", description: "TODO description" }
+  "Reproduction successful for issue #{issue_number}.\n\nReproduction Details:\n(Link to reproduction steps and results)" \
+  "Fix the bug" \
+  "Verify fix with reproduction steps"
+```
+
+**If NOT reproduced / Need info:**
+```bash
+# Create todo to follow up
+Call MCP `call_tool_todo_manager` { action: "create", priority: "p2", title: "Follow Up: Issue #{issue_number}", description: "TODO description" }
+  "Could not reproduce or need more info for issue #{issue_number}." \
+  "Request more information" \
+  "Attempt reproduction on different environment"
+```
+
+### Phase 5: Completion & Handoff
+
+#### Step 1: Establish Terminal UI State
+
+```javascript
+await task_boundary({
+  TaskName: "[COMPLETED] Reproduce Bug",
+  TaskStatus: "Reproduction attempt recorded. Offering next steps.",
+  Mode: "VERIFICATION",
+  TaskSummary: "Reproduction attempt for #{issue}. Result: {Reproduced/Not Reproduced}. Next steps persisted in todo."
+});
+```
+
+#### Step 2: Mandatory Handoff
+
+```bash
+✓ Reproduction attempt complete
+
+Next steps:
+1. /plan - Plan the fix (if reproduced)
+2. /report-bug - If new bug discovered during attempts
+3. /housekeeping - Cleanup context
+```
+
+---
+
+## References
+
+- Report bugs: `/report-bug`
+- Plan fix: `/plan`

package/skills/workflows/resolve_pr.md

@@ -1,133 +1,133 @@
----
-description: Handle PR comments and review feedback efficiently. Use when addressing reviewer feedback.
----
-
-# /resolve_pr - Address PR Feedback
-
-Work through PR comments and review feedback systematically.
-
-## When To Use
-
-- When a PR has review comments
-- After receiving change requests
-- To batch-process reviewer feedback
-
----
-
-## Workflow
-
-### Step 0: Search & Log
-
-```bash
-// turbo
-Call MCP `call_tool_logger_manager` { action: "logWorkflow", name: "/resolve_pr", outcome: "success" }
-Call MCP `call_tool_compound_manager` { action: "search", terms: [ "pull request review"] }
-```
-
-### Step 1: Fetch PR Comments
-
-```bash
-# Get PR details
-gh pr view {PR_NUMBER} --json comments,reviews
-
-# List requested changes
-gh pr view {PR_NUMBER} --json reviewRequests
-```
-
-### Step 2: Categorize Feedback
-
-Group comments by type:
-
-| Type | Action |
-|------|--------|
-| **Must fix** | Required for approval |
-| **Suggestion** | Consider implementing |
-| **Question** | Respond with clarification |
-| **Praise** | Acknowledge, no action needed |
-
-### Step 3: Address Each Comment
-
-For each must-fix comment:
-
-1. **Understand:** Read the feedback carefully
-2. **Fix:** Make the requested change
-3. **Test:** Verify the change works
-4. **Respond:** Reply to the comment
-
-```bash
-# After fixing
-git add -A
-git commit -m "fix: address review feedback - {description}"
-git push
-```
-
-### Step 4: Reply to Comments
-
-For each comment addressed:
-```bash
-gh pr comment {PR_NUMBER} --body "Fixed in {commit_sha}"
-```
-
-For questions:
-```bash
-gh pr comment {PR_NUMBER} --body "Good question - {explanation}"
-```
-
-### Step 5: Request Re-review
-
-```bash
-gh pr ready {PR_NUMBER}
-gh pr review {PR_NUMBER} --request
-```
-
-### Step 6: Summary
-
-```markdown
-## PR Feedback Addressed
-
-**Comments processed:** {X}
-**Changes made:** {Y}
-**Responses added:** {Z}
-
-### Changes Made:
-- Fixed: {description}
-- Updated: {description}
-
-### Awaiting Response:
-- Question about {topic}
-
-### Next Steps:
-1. Push changes: `git push`
-2. Request re-review
-3. Monitor for additional feedback
-```
-
-### Phase 5: Completion & Handoff
-
-#### Step 1: Establish Terminal UI State
-
-```javascript
-await task_boundary({
-  TaskName: "[COMPLETED] Resolve PR",
-  TaskStatus: "PR feedback addressed. Offering next steps.",
-  Mode: "VERIFICATION",
-  TaskSummary: "Addressed {count} comments on PR #{number}. Fixes verified and pushed."
-});
-```
-
-#### Step 2: Mandatory Handoff
-
-```bash
-✓ PR feedback resolved
-
-Next steps:
-1. /housekeeping - Cleanup branches
-2. /triage - Process any remaining feedback
-```
-
----
-
-## References
-
-- Review PRs: `/review`
-- Work on changes: `/work`
+---
+description: Handle PR comments and review feedback efficiently. Use when addressing reviewer feedback.
+---
+
+# /resolve_pr - Address PR Feedback
+
+Work through PR comments and review feedback systematically.
+
+## When To Use
+
+- When a PR has review comments
+- After receiving change requests
+- To batch-process reviewer feedback
+
+---
+
+## Workflow
+
+### Step 0: Search & Log
+
+```bash
+// turbo
+Call MCP `call_tool_logger_manager` { action: "logWorkflow", name: "/resolve_pr", outcome: "success" }
+Call MCP `call_tool_compound_manager` { action: "search", terms: [ "pull request review"] }
+```
+
+### Step 1: Fetch PR Comments
+
+```bash
+# Get PR details
+gh pr view {PR_NUMBER} --json comments,reviews
+
+# List requested changes
+gh pr view {PR_NUMBER} --json reviewRequests
+```
+
+### Step 2: Categorize Feedback
+
+Group comments by type:
+
+| Type | Action |
+|------|--------|
+| **Must fix** | Required for approval |
+| **Suggestion** | Consider implementing |
+| **Question** | Respond with clarification |
+| **Praise** | Acknowledge, no action needed |
+
+### Step 3: Address Each Comment
+
+For each must-fix comment:
+
+1. **Understand:** Read the feedback carefully
+2. **Fix:** Make the requested change
+3. **Test:** Verify the change works
+4. **Respond:** Reply to the comment
+
+```bash
+# After fixing
+git add -A
+git commit -m "fix: address review feedback - {description}"
+git push
+```
+
+### Step 4: Reply to Comments
+
+For each comment addressed:
+```bash
+gh pr comment {PR_NUMBER} --body "Fixed in {commit_sha}"
+```
+
+For questions:
+```bash
+gh pr comment {PR_NUMBER} --body "Good question - {explanation}"
+```
+
+### Step 5: Request Re-review
+
+```bash
+gh pr ready {PR_NUMBER}
+gh pr review {PR_NUMBER} --request
+```
+
+### Step 6: Summary
+
+```markdown
+## PR Feedback Addressed
+
+**Comments processed:** {X}
+**Changes made:** {Y}
+**Responses added:** {Z}
+
+### Changes Made:
+- Fixed: {description}
+- Updated: {description}
+
+### Awaiting Response:
+- Question about {topic}
+
+### Next Steps:
+1. Push changes: `git push`
+2. Request re-review
+3. Monitor for additional feedback
+```
+
+### Phase 5: Completion & Handoff
+
+#### Step 1: Establish Terminal UI State
+
+```javascript
+await task_boundary({
+  TaskName: "[COMPLETED] Resolve PR",
+  TaskStatus: "PR feedback addressed. Offering next steps.",
+  Mode: "VERIFICATION",
+  TaskSummary: "Addressed {count} comments on PR #{number}. Fixes verified and pushed."
+});
+```
+
+#### Step 2: Mandatory Handoff
+
+```bash
+✓ PR feedback resolved
+
+Next steps:
+1. /housekeeping - Cleanup branches
+2. /triage - Process any remaining feedback
+```
+
+---
+
+## References
+
+- Review PRs: `/review`
+- Work on changes: `/work`