From b57f098487d0c3c4ebc1db21f59eb623d7b94c9b Mon Sep 17 00:00:00 2001 From: Howard Enos Date: Sun, 19 Jul 2026 09:21:17 -0700 Subject: [PATCH] =?UTF-8?q?bug-tracker:=20add=20input-side=20check=20?= =?UTF-8?q?=E2=80=94=20look=20up=20matching=20issue=20before=20starting=20?= =?UTF-8?q?work?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The close-with-comment rule only covers the output side. Without checking the tracker when starting work, fixes get committed but matching issues stay open (exactly what happened with #13). Co-Authored-By: Claude Opus 4.6 (1M context) --- .claude/CLAUDE.md | 6 ++++-- .claude/SKILL_ROUTING.md | 5 +++++ 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/.claude/CLAUDE.md b/.claude/CLAUDE.md index a8360509..438ce76d 100644 --- a/.claude/CLAUDE.md +++ b/.claude/CLAUDE.md @@ -80,8 +80,10 @@ production, data-loss. Detail: EXTENDED + `.claude/OLLAMA.md`. tracking. If the bug is reproducible, affects a skill/tool/harness component, and won't be fixed in this session → file it as a Gitea issue via the `bug-tracker` skill (confirm title/priority with the user). The errorlog captures patterns for linting; the tracker - tracks resolution. When fixing a tracked bug, update/close the issue with a commit ref - comment — never close silently. See `SKILL_ROUTING.md` "Bug tracking" block. + tracks resolution. **When starting work on a bug/feature/skill task, check the tracker + for a matching issue first** — this is the step that connects the fix to the close. + When fixing a tracked bug, update/close the issue with a commit ref comment — never + close silently. See `SKILL_ROUTING.md` "Bug tracking" block. - **Log preventable friction too (`--friction`):** any time you waste tokens on a preventable, repeatable self-inflicted error — harness/env/tool misuse (Git-Bash `/tmp` path mismatch, shell env not persisting between Bash calls, passing huge args on the command line, PowerShell var case-collisions, etc.) — log it: `bash .claude/scripts/log-skill-error.sh "" "what wasted tokens + the fix" --friction [--context "ref="]`. **If it repeats something already in memory or CLAUDE.md, that's the highest-value entry** — it means a rule/memory isn't working; cite the ref. This log is the corpus we lint to build better CLAUDE.md rules and to clean stale/misleading memory. Goal: stop paying twice for the same mistake. - **Windows:** ensure `bash` resolves to Git-for-Windows MSYS bash, not the WSL stub; write `.claude/current-mode` with a relative/forward-slash path only (never a backslash Windows diff --git a/.claude/SKILL_ROUTING.md b/.claude/SKILL_ROUTING.md index 8969175f..b3603ed0 100644 --- a/.claude/SKILL_ROUTING.md +++ b/.claude/SKILL_ROUTING.md @@ -57,6 +57,11 @@ title/priority). This is in addition to `log-skill-error.sh` (the errorlog captu patterns; the tracker tracks resolution). Do NOT file: client machine problems, vendor API limitations, one-off env/friction issues already resolved, or transient errors. +When **starting work** on a bug, feature, or skill task, check the tracker first: +`py tracker.py list --repo --type ` — if a matching issue exists, note the +number and work against it. This is the step that connects "fix the thing" to "close the +issue" — skip it and the issue stays open after the fix is committed. + When **fixing** a tracked bug during a session, update the issue: 1. Add a progress comment if doing partial work 2. On fix: `py tracker.py close --comment "Fixed in . "`