← ClaudeAtlas

reconcile-trackerlisted

Reconcile the tracker against git — detect tickets whose recorded state contradicts what actually merged, plus stale claims. Read-only; it reports drift and never writes to the tracker. Use at session start, immediately after every merge, and whenever the tracker's accuracy is in question.
thientranhung/astragentic · ★ 4 · Code & Development · score 70
Install: claude install-skill thientranhung/astragentic
# Reconcile the tracker against git **The tracker is a claim. Git is evidence. This skill measures the distance.** Thomas owns the tracker, so this is Thomas's check. It is **read-only by design** — see "Why nothing here writes" before proposing to automate the fix. ## When it runs | Moment | Why | |---|---| | **Immediately after every merge** | This is where drift is BORN. The merge step already requires re-running the frontier and reporting what moved; this is the check that proves the write-back actually happened. | | **At session start** | Catches whatever the previous session left behind — including one that ended mid-dispatch. | | On the owner asking whether the tracker is accurate | The answer must be measured, never recalled. | A live project measured this the first time it wired the check in: four tickets sat in-progress with a live assignee **after their code was on the base branch**, the oldest by a full day. Nothing errored. The merge ran; the write-back did not; no artifact recorded the omission. That is AST-057 — *a step nothing reports is one nobody can tell was skipped.* ## Git is the oracle **Measure the tracker against git, never against itself.** A wrong ticket state is perfectly consistent with itself — in-progress with an assignee looks exactly like a real in-flight ticket — so a check reading only the tracker detects nothing. An oracle must be independent of what it measures: the same law that keeps a test's expected value out of the code under t