← ClaudeAtlas

github-issue-trackerlisted

Operating mechanics for a project whose tracker is GitHub Issues — status as labels, the claim, native dependencies keyed by database id, the frontier loop, and the Projects board mirror. Load it when the project's docs/agents/issue-tracker.md names GitHub. Read tracker-contract.md for what the pipeline requires of any tracker.
thientranhung/astragentic · ★ 4 · Code & Development · score 70
Install: claude install-skill thientranhung/astragentic
# Tracker adapter: GitHub Issues **Measured on a live project that moved Linear → GitHub on 2026-08-21.** Every trap below cost that project a run. What the pipeline requires of *any* tracker is `.agents/tracker-contract.md`; this file is the HOW for one of them. **The project half stays in the project.** This adapter carries nothing project-specific — the project's `docs/agents/issue-tracker.md` owns: the `<owner>/<repo>`, the ticket prefix, the label→board-column names, and that project's own decisions. Substitute those as you read. **The one fact that shapes everything:** GitHub Issues has **no status field**, so status lives in two unsynced places — the label, which is the truth, and the Project `Status` column, which is a mirror somebody has to write. Reach it with the **`gh` CLI**, not an MCP server. `gh` is already authenticated wherever PRs are already being driven, and an unproven tool path fails silently. ## Status is labels, and exactly one of them | Meaning | How it is stored | |---|---| | Backlog — not on the frontier | open + label `backlog` | | Todo — on the frontier, unclaimed | open + label `todo` | | In Progress — claimed | open + label `in-progress` + **assignee** | | Done | **closed** | | Won't fix | closed `--reason "not planned"` + label `wontfix` | | Duplicate | closed `--reason "not planned"` + label `duplicate` | Exactly one of `backlog` / `todo` / `in-progress` at a time, so a status change is two writes: ```bash gh issue edit <n> --remove-la