github-scanlisted

# GitHub Scan — Operational Skill This skill is the operational handbook for the `github-scan` product. If you have not yet loaded the `first-tree` entry-point skill, load that first — it explains the toolkit layout and the current canonical First Tree skill set. This skill covers _how_ to drive the `first-tree github scan` CLI. ## When To Use This Skill Load this skill when the task involves any of: - Running or inspecting the github-scan daemon - Viewing the GitHub notification inbox or the live activity feed - Triggering a one-off notification poll - Configuring, starting, or stopping the background daemon (launchd on macOS) - Installing the github-scan statusline hook into Claude Code - Diagnosing a broken github-scan install or a stuck claim GitHub Scan is designed for agents, not humans — most commands are idempotent and safe to re-run. ## Core Concepts - **Inbox** — the local store of explicit GitHub mentions and review requests, under `~/.first-tree/github-scan/`. - **Daemon** — a long-running broker process that polls GitHub, keeps the inbox fresh, dispatches work to per-task agent runners, and serves a local HTTP/SSE endpoint on `127.0.0.1:7879` for the dashboard. - **Runner** — a per-task worker spawned by the daemon for a single claim. - **Claim** — exclusive lease on a notification so only one runner acts on it. - **Statusline** — a sub-30 ms Claude Code statusline hook that prints a one-line summary of the inbox state. ## CLI Commands ### Primary