---
name: Tracker comment discipline
description: Every issue state change (fix, close, progress, block) MUST have a comment in the Gitea issue explaining what was done, with commit refs. No silent closes. No issues left without a trail.
type: feedback
---

When fixing a bug, closing an issue, or making progress on any tracked item, ALWAYS add a comment to the Gitea issue via the bug-tracker skill BEFORE or AT the time of the state change.

**Why:** Issues were being closed without comments, fixes were committed without updating the tracker, and status lived in FEATURE_ROADMAP.md but never flowed back to the issues. Mike opened the tracker and saw stale/wrong status because nobody went back to update the issues. The whole point of the tracker is the comment trail.

**How to apply:**
- When a fix is committed: `py tracker.py comment <repo> <num> --body "Fixed in commit <sha>. <what was done>"`
- When closing: always use `--comment` flag: `py tracker.py close <repo> <num> --comment "reason"`
- When making progress: add a comment describing what was tried/done
- When a session discovers an issue is already fixed: verify in code, add the verification comment with commit refs, then close
- Never close an issue silently — the comment IS the documentation
- Check FEATURE_ROADMAP.md status against tracker status and reconcile discrepancies
