update-progress
Verify a session's handoff document and update the repo's docs and kanban board from it. Run in a fresh session after session-handoff.
- License 许可
- MIT
- 所属仓库
- KrishP147/skills
- 最近更新
- 2026-11-10
- Stars
- ★ 37
- Forks
- 1
01 前言 Front Matter
- name
- update-progress
- description
- Verify a session's handoff document and update the repo's docs and kanban board from it. Run in a fresh session after session-handoff.
- argument-hint
- handoff doc path (default: newest by mtime in the handoff folder)
02 资源文件 1
- 参考文档README.md6.1 KB
03 SKILL.md 正文
Treat every claim in the handoff as unverified until you've checked it.
- Locate the handoff: given path, else the newest by mtime among
*.mdin the handoff folder (AGENTS.md/CLAUDE.md's, elseskilleddocs/handoffs/) in everygit worktree listentry (current worktree first; an uncommitted handoff lives in the task's worktree). In the other worktrees count only untracked files (git -C <wt> ls-files --others -- <folder>, no--exclude-standard: untracked mode excludes the folder); their tracked handoffs are checkout copies of committed ones, stamped with checkout time. Skip one whose issues all carry a "verified, merged" comment (already processed); one closed by a PR'sCloses #nwithout it still runs, for the docs. Tied mtimes → list them and ask. None → newest handoff-looking file in the OS temp dir. - Verify:
git fetch originfirst.git logover the handoff's base SHA..head, elsegit merge-base <default> <branch>..branch (<default>per thehandoff-autoskill'sTRACKING.md). Merged = head is an ancestor oforigin/<default>(git merge-base --is-ancestor <head> origin/<default>), or the branch has a merged PR containing head (gh pr list -R <owner>/<repo> --head <branch> --state merged --json number,headRefOid;<owner>/<repo>per BOARD.md): head ==headRefOid→ merged; elsegit fetch origin pull/<number>/head(the PR branch is often deleted after merge; GitHub keeps the PR ref), thengit merge-base --is-ancestor <head> <headRefOid>. A fetch or command that errors (missing object, exit other than 0 or 1) is never merged. Squash and rebase merges never make head an ancestor, and a stale local<default>misses fresh merges. Decide merged per issue for steps 4–5: head merged, or the issue is closed by a merged PR (gh issue view <n> -R <owner>/<repo> --json state,closedByPullRequestsReferences, then that PR'sheadRefOid) whose head is in the range (git merge-base --is-ancestor <headRefOid> <head>); one issue merging mid-session doesn't wait for the rest. Run the repo's test command on the code the handoff describes: merged → the<default>checkout aftergit pull --ff-only(won't fast-forward → a tempgit worktree add --detach <tmp> origin/<default>); else the worktree with<branch>checked out at head, else a tempgit worktree add --detach <tmp> <head>(install deps there first; remove it after). Record the real result and where it ran. - Review: product code changed → call the Skill tool with
"code-review"on the session's commits. - Docs, only for merged issues and only what the repo already has; a protected
<default>(step 7) → switch to its docs branch before editing: tick roadmap checkboxes, add status/CHANGELOG entries, add a decisions row if the handoff records a decision.- The "current phase" marker follows where merges land. Merges in a later phase → move the marker; mark the earlier phase "done except gated (#…)".
- Every capability merged this phase appears in the README / status summary. A missing one is drift; fix it here.
- Board (BOARD.md; its Target repo section first:
-Ron everyghcall, on a fork ask before writing): comment a summary on each issue. Per issue: complete, verified and merged → Done, close the issue, comment "verified, merged". Complete and verified, not merged → In Review, comment "verified, awaiting merge" (the PR'sCloses #nor a later run closes it). Otherwise set the status to where it really stands. - Deviations in
## Board status→ call the Skill tool with"consult-plan". - Commit in the
<default>checkout, on<default>, or when it is protected on the docs branchdocs/progress-<issue>[-<issue>…](thehandoff-autoskill'sTRACKING.md, "Protected<default>": test, branch, push gate): the step-4 doc edits, plus the handoff if it is uncommitted and thatTRACKING.mdsays commit mode (untracked mode → leave it). A handoff in another worktree: move it into the<default>checkout's handoff folder first (left there, it blocks that branch's next merge). - Finish with the
nextskill.
04 同仓库更多 Skills
wayfinder
Plan an effort too big for one session as a map of decision tickets (GitHub issue + sub-issues) and resolve them one per session until the way is clear, then hand off to divide.
skill
暂无简介
teammate-brief
Write an onboarding document for a person joining or picking up a project — what it is, setup steps verified by running them, env var names and where to get them, tasks with "done when", owners, don't-touch list. Use for "brief my teammate", "onboarding doc for X", "hand this project to someone".
switch
Move this conversation to another Claude account (the previous one, or one by name), or set up, add, remove, rename and list accounts.
spend-gate
Gate any billable action (GPU pods/instances, paid APIs or tiers, cloud credits) behind a cost estimate, a live balance check, and an explicit yes for that action. Use before any create/deploy on a paid provider (runpodctl, vultr-cli, aws/gcloud/az, modal, provider MCP create/deploy/run/start/update), any paid API call, or when spend-guard blocks one.
sitrep
Live status of this session in ≤10 lines — what's running, git state, PRs + CI, asked vs done, what needs the user, and a SAFE/NOT SAFE close verdict. Use for "how's it going", "status update", "what's running", "can I close this".