Release v0.1.0: 小程序使用建议跳转腾讯文档 + 配置导入导出功能

2026-05-04 17:09:07 +08:00
commit 7d90523164
89 changed files with 18289 additions and 0 deletions
@@ -0,0 +1,53 @@
+---
+name: bugpack-fix-bug
+description: "Fix a bug from BugPack by reading its context, locating code, applying fixes, and updating status. Use when: user asks to fix, repair, or resolve a bug. NOT for: just listing bugs (use bugpack-list-bugs) or just viewing bug details (use bugpack-view-bug)."
+metadata:
+  openclaw:
+    emoji: "\U0001F527"
+---
+
+# BugPack - Fix Bug
+
+Read bug context from BugPack, locate the relevant code, apply a fix, and mark the bug as fixed.
+
+## Instructions
+
+1. **Get bug context**: Call `GET http://localhost:3456/api/bugs/:id` to fetch full bug details including description, screenshots, environment, and related files.
+
+2. **Analyze the bug**: Read the description and examine the screenshots to understand what is broken and what the expected behavior should be.
+
+3. **Locate code**: Use the `relatedFiles` array from the bug context to find the relevant source files. If `relatedFiles` is empty, use the `pagePath` and `description` to search the codebase.
+
+4. **Apply fix**: Edit the source code to fix the described issue. Follow the project's existing code style and conventions.
+
+5. **Mark as fixed**: After applying the fix, call `PATCH http://localhost:3456/api/bugs/:id` with:
+   ```json
+   { "status": "fixed" }
+   ```
+
+6. **Add fix note** (optional): Call `PATCH http://localhost:3456/api/bugs/:id` with a description update to document what was changed.
+
+## Example
+
+```bash
+# Step 1: Get bug context
+GET http://localhost:3456/api/bugs/abc-123
+
+# Step 5: Mark as fixed
+PATCH http://localhost:3456/api/bugs/abc-123
+Content-Type: application/json
+
+{ "status": "fixed" }
+```
+
+Response:
+
+```json
+{
+  "ok": true,
+  "data": {
+    "id": "abc-123",
+    "status": "fixed"
+  }
+}
+```
@@ -0,0 +1,42 @@
+---
+name: bugpack-list-bugs
+description: "List all tracked bugs from BugPack with status and project filtering. Use when: user asks about bugs, pending issues, bug lists, or wants to see what needs fixing. NOT for: viewing detailed bug context (use bugpack-view-bug) or fixing bugs (use bugpack-fix-bug)."
+metadata:
+  openclaw:
+    emoji: "\U0001F41B"
+---
+
+# BugPack - List Bugs
+
+Query the BugPack local server to list all tracked bugs.
+
+## Instructions
+
+1. Call `GET http://localhost:3456/api/bugs` to fetch all bugs.
+   - Optional query param: `?project_id=<id>` to filter by project.
+2. Parse the JSON response. Each bug has: `id`, `title`, `description`, `status`, `priority`, `project_id`, `created_at`, `updated_at`.
+3. Present the list in a readable table format, grouped by status (`open` / `fixed` / `closed`).
+4. If no bugs are found, tell the user there are no tracked bugs.
+
+## Example
+
+```
+GET http://localhost:3456/api/bugs
+```
+
+Response:
+
+```json
+{
+  "ok": true,
+  "data": [
+    {
+      "id": "abc-123",
+      "title": "Button click not working",
+      "status": "open",
+      "priority": "high",
+      "created_at": "2026-03-15T10:00:00Z"
+    }
+  ]
+}
+```
@@ -0,0 +1,57 @@
+---
+name: bugpack-view-bug
+description: "View detailed bug context from BugPack including screenshots, environment info, and related files. Use when: user wants to see bug details, screenshots, or understand a specific bug before fixing. NOT for: listing all bugs (use bugpack-list-bugs) or directly fixing bugs (use bugpack-fix-bug)."
+metadata:
+  openclaw:
+    emoji: "\U0001F50D"
+---
+
+# BugPack - View Bug Details
+
+Fetch full bug context from BugPack, including description, screenshots, environment info, and related files.
+
+## Instructions
+
+1. Call `GET http://localhost:3456/api/bugs/:id` to get the full bug details.
+2. The response includes:
+   - `title`, `description`, `status`, `priority`
+   - `pagePath` — the page/route where the bug occurs
+   - `device`, `browser` — environment info
+   - `relatedFiles` — array of file paths related to the bug
+   - `screenshots` — array of screenshot objects with `id`, `name`, `original_path`, `annotated_path`
+3. Display the bug info in a structured format.
+4. If the bug has screenshots, mention them and offer to show annotated versions.
+5. If `relatedFiles` are listed, use them to locate relevant source code.
+
+## Example
+
+```
+GET http://localhost:3456/api/bugs/abc-123
+```
+
+Response:
+
+```json
+{
+  "ok": true,
+  "data": {
+    "id": "abc-123",
+    "title": "Button click not working",
+    "description": "The submit button on the login page does not respond to clicks",
+    "status": "open",
+    "priority": "high",
+    "pagePath": "/login",
+    "device": "Desktop",
+    "browser": "Chrome 120",
+    "relatedFiles": ["src/pages/Login.tsx", "src/components/SubmitButton.tsx"],
+    "screenshots": [
+      {
+        "id": "ss-001",
+        "name": "login-bug.png",
+        "original_path": "/uploads/MyProject/original.png",
+        "annotated_path": "/uploads/MyProject/annotated.png"
+      }
+    ]
+  }
+}
+```
@@ -0,0 +1,83 @@
+---
+name: bugpack
+description: "BugPack - AI-powered bug tracking and fixing toolkit. List bugs, view bug details with screenshots, and fix bugs automatically. Includes three workflows: list-bugs, view-bug, fix-bug. Requires BugPack server running locally."
+metadata:
+  openclaw:
+    emoji: "\U0001F4E6"
+---
+
+# BugPack
+
+AI-powered bug tracking and fixing toolkit. List, view, and fix bugs from BugPack.
+
+## Prerequisites
+
+Start BugPack server first:
+
+```bash
+npx bugpack-mcp
+```
+
+## Skill 1: List Bugs
+
+Query all tracked bugs with optional filtering.
+
+### Instructions
+
+1. Call `GET http://localhost:3456/api/bugs` to fetch all bugs.
+   - Optional: `?project_id=<id>` to filter by project.
+2. Each bug has: `id`, `title`, `description`, `status`, `priority`, `project_id`, `created_at`.
+3. Present results grouped by status (`pending` / `fixed` / `closed`).
+
+### Example
+
+```
+GET http://localhost:3456/api/bugs
+```
+
+---
+
+## Skill 2: View Bug Details
+
+Fetch full bug context including screenshots, environment, and related files.
+
+### Instructions
+
+1. Call `GET http://localhost:3456/api/bugs/:id` for full details.
+2. Response includes: `title`, `description`, `status`, `priority`, `pagePath`, `device`, `browser`, `relatedFiles`, `screenshots`.
+3. Use `relatedFiles` to locate relevant source code.
+4. Screenshots have `original_path` and `annotated_path`.
+
+### Example
+
+```
+GET http://localhost:3456/api/bugs/abc-123
+```
+
+---
+
+## Skill 3: Fix Bug
+
+Read bug context, locate code, apply fix, and update status.
+
+### Instructions
+
+1. **Get context**: `GET http://localhost:3456/api/bugs/:id`
+2. **Analyze**: Read description and examine screenshots.
+3. **Locate code**: Use `relatedFiles` or search by `pagePath` and `description`.
+4. **Apply fix**: Edit source code following project conventions.
+5. **Mark fixed**: `PATCH http://localhost:3456/api/bugs/:id` with `{ "status": "fixed" }`
+6. **Add note** (optional): Update description to document what was changed.
+
+### Example
+
+```bash
+# Get bug context
+GET http://localhost:3456/api/bugs/abc-123
+
+# Mark as fixed
+PATCH http://localhost:3456/api/bugs/abc-123
+Content-Type: application/json
+
+{ "status": "fixed" }
+```