---
name: Auto-file bugs to tracker when found
description: When a bug or error surfaces during a session, file it as a Gitea issue via the bug-tracker skill immediately — do not rely on someone remembering later.
type: feedback
---

Bugs found during sessions were getting lost because they were only logged to errorlog.md (a flat file nobody checks proactively) or mentioned in session logs (buried in narrative). The tracker exists to make bugs visible.

**Why:** Howard and Mike built the tracker specifically because "bug fixes are getting dropped and forgotten." The errorlog captures errors but doesn't track resolution. The wiki captures knowledge but doesn't track status. Only the tracker (Gitea issues) has status, priority, assignee, and comment history.

**How to apply:**
- When a skill fails with a real bug (not a transient/env issue): file it via `py .claude/skills/bug-tracker/scripts/tracker.py create ...`
- When the user reports something broken: confirm the title/priority with them, then file it
- Still log to errorlog.md (that's the pattern corpus for linting), but ALSO file the tracker issue
- Do NOT file: client machine problems, vendor API limitations, one-off env issues
- DO file: skill bugs, harness bugs, RMM code bugs, dashboard bugs, script failures that need follow-up
