\r \r

BugPack\r

\r AI-powered bug tracking and fixing toolkit. List, view, and fix bugs from BugPack.\r \r

Prerequisites\r

\r Start BugPack server first:\r \r

npx bugpack-mcp\r
```\r
\r
## Skill 1: List Bugs\r
\r
Query all tracked bugs with optional filtering.\r
\r
### Instructions\r
\r
1. Call `GET http://localhost:3456/api/bugs` to fetch all bugs.\r
   - Optional: `?project_id=\x3Cid>` to filter by project.\r
2. Each bug has: `id`, `title`, `description`, `status`, `priority`, `project_id`, `created_at`.\r
3. Present results grouped by status (`pending` / `fixed` / `closed`).\r
\r
### Example\r
\r
```\r
GET http://localhost:3456/api/bugs\r
```\r
\r
---\r
\r
## Skill 2: View Bug Details\r
\r
Fetch full bug context including screenshots, environment, and related files.\r
\r
### Instructions\r
\r
1. Call `GET http://localhost:3456/api/bugs/:id` for full details.\r
2. Response includes: `title`, `description`, `status`, `priority`, `pagePath`, `device`, `browser`, `relatedFiles`, `screenshots`.\r
3. Use `relatedFiles` to locate relevant source code.\r
4. Screenshots have `original_path` and `annotated_path`.\r
\r
### Example\r
\r
```\r
GET http://localhost:3456/api/bugs/abc-123\r
```\r
\r
---\r
\r
## Skill 3: Fix Bug\r
\r
Read bug context, locate code, apply fix, and update status.\r
\r
### Instructions\r
\r
1. **Get context**: `GET http://localhost:3456/api/bugs/:id`\r
2. **Analyze**: Read description and examine screenshots.\r
3. **Locate code**: Use `relatedFiles` or search by `pagePath` and `description`.\r
4. **Apply fix**: Edit source code following project conventions.\r
5. **Mark fixed**: `PATCH http://localhost:3456/api/bugs/:id` with `{ "status": "fixed" }`\r
6. **Add note** (optional): Update description to document what was changed.\r
\r
### Example\r
\r
```bash\r
# Get bug context\r
GET http://localhost:3456/api/bugs/abc-123\r
\r
# Mark as fixed\r
PATCH http://localhost:3456/api/bugs/abc-123\r
Content-Type: application/json\r
\r
{ "status": "fixed" }\r
```\r