blob: bf4835704b411e72913de6b51a7fbe1b0ce0c600 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
---
name: bug-manager
description: Manage, list, and resolve production bugs using custom project scripts. Use when investigating reported errors, viewing production logs, or marking bugs as resolved in the dashboard's database.
---
# Bug Manager
This skill formalizes the workflow for handling production bugs in the `doot` project.
## Workflow
### 1. Identify Bugs
- Run `./scripts/bugs` to list currently open production bugs.
- Each bug has an `id`, a `description`, and a `created_at` timestamp.
### 2. Diagnose with Logs
- Use `./scripts/logs` to investigate.
- For recent errors: `./scripts/logs -n 100`
- To filter for errors: `./scripts/logs --grep "error"`
- Refer to [references/bug-triage.md](references/bug-triage.md) for common error patterns.
### 3. Fix and Verify
- Implement a reproduction test locally.
- Apply the fix.
- Deploy via `./scripts/deploy`.
### 4. Resolve
- Mark the bug as resolved using `./scripts/resolve-bug <id>`.
- This script also displays the bug description before deletion for confirmation.
## Quick Start
- "List all production bugs" -> `./scripts/bugs`
- "Show me the last 50 lines of production logs" -> `./scripts/logs -n 50`
- "Mark bug #12 as resolved" -> `./scripts/resolve-bug 12`
|
