BuzzbeeSCD/openchamber
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(commands): source bug-work from the root-cause:found label only

Browse Source 
The command ships in the public repo; the local triage backlog file is
maintainer-private and not a dependency anyone else can resolve.
This commit is contained in:
Bohdan Triapitsyn
2026-08-28 13:54:27 +03:00
parent 198d3f12d1
commit 262397f896
1 changed files with 3 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.opencode/commands/bug-work.md
+3 -5
View File
@@ -6,10 +6,8 @@ Focus, if any: $ARGUMENTS
The maintainer wants to fix real bugs without touching the GitHub UI. Run this as a conversation, not a report:
1. **Gather the menu.** Two sources, both verified:
- the local backlog at `.opencode/plans/issue-triage/fix-backlog.md` — LIVE bugs with current file:line anchors, grouped by area, data-loss first;
- `gh issue list -R openchamber/openchamber --state open --label root-cause:found --json number,title,labels` for anything newer than the backlog file.
1. **Gather the menu.** `gh issue list --state open --label root-cause:found --json number,title,labels,comments` — bugs whose intake comment cites a traced mechanism with file:line.
2. **Propose 3–5 candidates**, one line each: the user-visible symptom, the traced mechanism (file:line), and rough size. Order by severity: data-loss and regression first, then whatever matches the maintainer's focus (an area, a platform, "щось маленьке"). Ask which to take — batches of related small fixes in one area are welcome.
3. **Verify before fixing.** Anchors age: confirm the cited mechanism still exists on current main (main moves fast — see the backlog header). If it is gone, say so and mark the issue for a fixed-close instead of fixing air.
3. **Verify before fixing.** Anchors age: confirm the cited mechanism still exists on current main (main moves fast). If it is gone, say so and mark the issue for a fixed-close instead of fixing air.
4. **Fix properly.** Follow AGENTS.md instruction order (matching skills — sync bugs demand `sync-state-invariants`, hot paths `performance-engineering`); minimal fix plus a regression test per local precedent; focused validation.
5. **Close the loop.** When the maintainer confirms and asks to commit, include `fixes #<N>` per bug in the commit message so GitHub closes the issues automatically. Update the backlog file: remove the fixed entries. Never commit or push without being asked.
5. **Close the loop.** When the maintainer confirms and asks to commit, include `fixes #<N>` per bug in the commit message so GitHub closes the issues automatically. Never commit or push without being asked.