bug
/bug
Open, show, update, link, or close a bug in the tracker, with a duplicate-title check before every open. A bug is a lasting tool or system defect. Use for /bug open, /bug show, /bug link, /bug close, or when someone says file a bug or this tool is broken.
- Author
- foxrun-ai ↗
- Repository
- foxrun ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Open, show, update, link, or close a bug in the tracker, with a duplicate-title check before every open. A bug is a lasting tool or system defect. Use for /bug open, /bug show, /bug link, /bug close, or when someone says file a bug or this tool is broken.
Arguments
/bug open | show | update | link | close <bug id or title words>
Original author description
Open, show, update, link, or close a bug in the tracker, with a duplicate-title check before every open. A bug is a lasting tool or system defect. Use for /bug open, /bug show, /bug link, /bug close, or when someone says file a bug or this tool is broken.
How it works
- Find the tracker
- Steps
- Gotchas
SKILL.md preview
--- type: note workspace: system timestamp: 2026-10-26T14:10:00-04:00 name: bug description: "Open, show, update, link, or close a bug in the tracker, with a duplicate-title check before every open. A bug is a lasting tool or system defect. Use for /bug open, /bug show, /bug link, /bug close, or when someone says file a bug or this tool is broken." kind: knowledge argument-hint: "open | show | update | link | close <bug id or title words>" --- # bug One skill for the bug object. A bug is a lasting defect in a tool or a system. A defect with a start time and an impact is also an incident: open it with `<work> incident-open` and link the bug. A bug closes as `fixed` only through a task that fixes it, so the fix has an owner and evidence. ## Find the tracker Set `<ws>` to the workspace that owns the work. Do not route by the current folder alone. Set `<tracker>` to `workspace_settings.<ws>.database` in `~/.foxrun/config/person.json`. If it is absent, use `~/.foxrun/data.db`. In the commands below, `<work>` stands for this exact prefix: ```bash python3 ~/.foxrun/work/work.py --workspace <ws> --db <tracker> --receipt-root ~/foxrun/<ws> --by <you> ``` Write `<you>` as your own agent name, never the runtime name. ## Steps 1. **Check for a duplicate first.** Before any `open`, run: `sqlite3 -readonly <tracker> "SELECT id,title,status,capability FROM bugs WHERE title LIKE '%<words>%' OR capability LIKE '%<words>%' ORDER BY created_on"`. If an open bug fits, add to it with `bug-update` or a comment. Done when you named the match, or said there is none. 2. **Run the operation.** Done when the command prints `ok`. | Operation | Command | |---|---| | open | `<work> bug-open --id B-<yyyymmdd>-<short-slug> --title "<defect>" --capability "<capability>" --description "<what fails>" --problem ... --job-when ... --job-want ... --job-so ... --body "<what the fix changes>" --acceptance ... --context ... --where <path>` | | update | `<work> bug-update <bug id> --add-tag <tag> --context "<new evidence>"` | | link to a fix | `<work> link <bug id> --subject-type bug --target-type task --target-id <task id> --relation fix` | | close | `<work> bug-close <bug id> --status fixed --note "<task id> fixes it"` | | close, no fix | `<work> bug-close <bug id> --status wont-fix --note "<reason>"` | 3. **Read it back.** Run `sqlite3 -readonly <tracker> "SELECT id,title,status,capability FROM bugs WHERE id='<bug id>'"`. Done when the row shows the status you expect. ## Gotchas - `bug-close --status fixed` refuses a bug with no `fix` link to a task. Link first. - A bug is not a task. The task that fixes it holds the work and the runs. - `link` also takes `--relation caused-by`, `found-in`, `updated`, and `about`. Run `<work> link -h`.
Files in this package (2)
- SKILL.md 3 KB
- replays/close-needs-fix-link.json 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · foxrun-ai/foxrun | 100 | MIT |
| Perchusha/pitwall | 100 | MIT |
| lucas-saldanha-werneck/handoff-terminal | 100 | MIT |
| jisuzzzz/haechi | 100 | MIT |
| paulhowever/orchestor | 100 | MIT |
| AtT6669/dsh-go-root | 82 | AGPL-3.0 |
Database snapshot: 13.11.2026 · package version 6217fbca9688 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 91obsidian-tracker-bug-close
Close a bug report in Obsidian project. Use when the user invokes /bug-close. - 100task
Create, show, claim, finish, or move a task in a tracker with a duplicate-title check before every create. Use for /task create, /task show, /task claim, /task done, /task move, /task backlog, or when someone says add a task, close the task, or what is T123. - 100stream
Create, show, or rename a work stream in the tracker with a duplicate-title check before every create. A work stream is a projects row. Use for /stream create, /stream show, /stream rename, /stream order, or when someone asks what a work stream holds. - 100jira-bug-ticket
Create a Jira bug ticket. Use when the user asks to file, log, report, or create a bug or defect in Jira ("create a bug ticket", "log a bug", "report a bug", "open a ticket for this bug"). - 95obsidian-tracker-project-bug
Create or update a bug report in Obsidian. Use when the user invokes /project-bug. - 90issue-tracker
File, update, and close GitHub work as one epic with native sub-issues. Use when the user asks to file, track, update, or close a GitHub issue, or to open, update, or refresh an epic and its sub-issues.