diff options
| author | Agando <roduccomm@gmail.com> | 2026-06-02 18:00:37 +0200 |
|---|---|---|
| committer | Agando <roduccomm@gmail.com> | 2026-06-02 18:00:37 +0200 |
| commit | aafb0fbde5289a45f9f818a00141f80b149be283 (patch) | |
| tree | d4d8f588187719c99240fbaef1940c068402b892 /skills/bug-tracker.md | |
| parent | 6d41e590a38c73ef60f1c04beaf8f5438f350f46 (diff) | |
auto: 2026-06-02_18:00 changes
Diffstat (limited to 'skills/bug-tracker.md')
| -rw-r--r-- | skills/bug-tracker.md | 30 |
1 files changed, 30 insertions, 0 deletions
diff --git a/skills/bug-tracker.md b/skills/bug-tracker.md new file mode 100644 index 0000000..05963e4 --- /dev/null +++ b/skills/bug-tracker.md @@ -0,0 +1,30 @@ +--- +name: bug-tracker +description: A systematic approach to tracking and managing bugs in the VFS. +tags: [dev, debugging, management, workflow] +--- + +# 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". |