From ccc7d9956559d2195e20345e7a794662b52cd403 Mon Sep 17 00:00:00 2001 From: Agando Date: Sat, 6 Jun 2026 06:00:27 +0200 Subject: auto: 2026-06-06_06:00 changes --- skills/bug-tracker.md | 31 ------------------------------- 1 file changed, 31 deletions(-) delete mode 100644 skills/bug-tracker.md (limited to 'skills/bug-tracker.md') diff --git a/skills/bug-tracker.md b/skills/bug-tracker.md deleted file mode 100644 index bb8febf..0000000 --- a/skills/bug-tracker.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -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". -- cgit v1.2.3