Menu
Drive recurring GitHub issue work from shipped slices to final closeout or reusable closed-issue audits.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | issue-watch-closeout |
| description | Drive recurring GitHub issue work from shipped slices to final closeout or reusable closed-issue audits. |
.agents/skills/issue-contract-expansion/SKILL.md first./.git/helpers/gh-appAGENTS.mdREADME.mdhandoff.mdactive, prepared, or writing slices left for the issueMarker: issue-watch-closeout note with Status: validation-ready and Slice: issue-closeout; treat that comment as the reusable closeout source commentorigin/main, then do one final read-only recheck against the issue ask on current mainStatus: done, close the issue, and release the closeout sliceissue-watch-closed-audit note with the latest shipped change plus current main; if that note already covers the same-or-newer origin/main state and the issue thread has not changed since then, skip the thread write and keep any repeat no-op note only in a bounded repo-local operator surface when it changes handoff stateMarker: issue-watch-closed-audit note and update it in place with the fresh recheckvalidated comments may still be left as extra signal, but they are never a closure gateorigin/main immediately before the final closeout recheckblocked, released, or a new mapped note insteadvalidation-ready when the same editable closeout comment can be updated to donenode tools/issue-watch-comment-upsert.mjs for reusable source-slice, closeout, and closed-audit comments instead of ad hoc append-only gh issue comment callsissue-watch-closed-audit comment per closed issueorigin/main nor the issue thread has advanced since the last audit; repeat no-change checks belong in repo-local handoff/operator state only when they change current state, not the issue threadOptacbook[bot] identityvalidation-ready note when closeout starts and that same note is edited in place to Status: doneissue-watch-closed-audit note that gets updated in place on later review runsorigin/main, rereads the shipped outcome, and updates the reusable closeout comment before closureissue-watch-closed-audit note in place instead of growing the thread with duplicate auditsghValidate integrity of all public/data JSON files. Use when: after editing candidates, constituencies, or districts JSON; before committing data changes; checking coverage completeness; debugging data mismatches.
Refresh public district candidate rows from structured live-field research plus staged facts/timelines. Use when: surfacing all candidates per constituency in the app, resyncing public/data after research candidate changes, or restoring legacy candidate route aliases.
Wrap up a meaningful repo work session. Use when: folding durable learnings into repo-local skills, syncing AGENTS/README/handoff docs, or preparing the final close-out commit and push.
Work one bounded constituency possible-outcome slice. Use when: creating or reviewing seat-local outcome packets under the new 1 primary + 3 reviewer workflow.
UI rules for the Kerala elections app. Use when: modifying components, adding status indicators, changing how candidates or constituencies display, or touching motion.
Maintain the internal-only constituency outlook ledger. Use when: adding or revising seat outlook labels, rationale, risk factors, or source bundles in research/statewide/constituency-outlooks.json.