blob: bb8febf4dbc4341e12c041503c23839c0aeb18d2 (
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
|
---
name: bug-tracker
description: A systematic approach to tracking and managing bugs in the VFS.
tags: [dev, debugging, management, workflow]
category: dev
---
# Bug Tracking Workflow
This skill provides a standardized way to track bugs using a JSON-based log file in the root directory.
## 1. Initialize Bug Log
If `/bugs.json` does not exist, create it with an empty array: `[]`.
## 2. Reporting a Bug
When a bug is found, append a new entry to `/bugs.json` with the following schema:
- `id`: Unique incremental integer.
- `title`: Brief summary of the issue.
- `description`: Detailed steps to reproduce and expected vs actual behavior.
- `status`: "open" | "in-progress" | "resolved" | "closed".
- `severity`: "low" | "medium" | "high" | "critical".
- `created_at`: Timestamp.
- `updated_at`: Timestamp.
## 3. Managing Bugs
- **List Open Bugs**: Filter `/bugs.json` for entries where `status != "closed"`.
- **Update Status**: Change the `status` and update the `updated_at` timestamp.
- **Resolve**: Mark as "resolved" and add a `resolution` field explaining the fix.
## 4. Verification
Once a bug is marked "resolved", run existing tests or manually verify the fix before marking it "closed".
|
