← ClaudeAtlas

hey-synclisted

Bring the ledger up to date — check boxes, recount progress, reorder what is next. Use on "update the ledger", "sync the checklist", "recount progress", "reflect current status", "pull in the merged PRs". Edits in place; never creates a new file.
keenkim1202/Hey · ★ 1 · Data & Documents · score 67
Install: claude install-skill keenkim1202/Hey
# Updating the ledger ```bash ROOT="${CLAUDE_PLUGIN_ROOT:-$PLUGIN_ROOT}" # Codex names it PLUGIN_ROOT HEY="$ROOT/scripts/hey.py" BOARD="$ROOT/scripts/board.py" ``` **Never rewrite the whole file.** Edit only the lines that changed. Estimates, unfinished items, blocker tables and out-of-scope tables have reasoning behind them — never delete or recompute them on a whim. ## 1. Find what landed The "last synced" line at the top of the ledger holds the reference commit. Look past it. ```bash cd <project root> git fetch origin --quiet git log --oneline <reference commit>..origin/<default branch> gh pr list --state all --limit 30 --json number,title,createdAt,mergedAt,state \ -q '.[] | [.number, (.createdAt|split("T")[0]), (if .mergedAt then (.mergedAt|split("T")[0]) else "-" end), .state, .title] | @tsv' | sort -n ``` **Never trust a PR title.** One titled "module scaffold" may be two lines of `Placeholder.swift`. Run `git show --stat <commit>` and see what actually landed. **Confirm completion in the code**, by file listing or symbol presence — not by title. If PR bodies carry `closes <item key>` markers, collect them: ```bash python3 "$HEY" pr-sync ``` That command **only finds them; it never checks anything off.** Verify in the code first. ## 2. Do not keep a PR log There used to be a table here to append to. **Do not recreate it.** GitHub already holds the authoritative, searchable, append-only record of every PR with its open and merge dates, and a second copy