From 8abc63efdbc0bb96cd6c9aa99d6e9166e0bcabae Mon Sep 17 00:00:00 2001 From: Peter Stone Date: Sun, 22 Mar 2026 23:45:19 +0000 Subject: chore: unify and centralize agent configuration in .agent/ --- bug-manager/SKILL.md | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 bug-manager/SKILL.md (limited to 'bug-manager/SKILL.md') diff --git a/bug-manager/SKILL.md b/bug-manager/SKILL.md new file mode 100644 index 0000000..bf48357 --- /dev/null +++ b/bug-manager/SKILL.md @@ -0,0 +1,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 `. +- 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` -- cgit v1.2.3