# Change Closure

> Use only after an explicit request to verify completion or when an applicable safety, contract, or lifecycle gate requires closure. Check fresh verification, affected contract surfaces, stale identifiers, authoritative records, and intentional leftovers. Do not trigger for ordinary authorized implementation changes, read-only analysis, or drafts.

- Skill: `xiongweilin/change-closure` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add xiongweilin/change-closure`
- Raw SKILL.md: https://api.skillmd.com/api/skills/xiongweilin/change-closure/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: xiongweilin (https://skillmd.com/u/xiongweilin)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/xiongweilin/change-closure

---


# Change Closure

Use this checklist only after an explicit request to verify completion or when an applicable safety, contract, or lifecycle gate requires closure. Do not reopen the whole design unless a check fails.

## Closure checks

- **Fresh proof:** run the smallest relevant test, diff, exit-status, endpoint, or file check.
- **Contract sync:** update only the README, API/config docs, schemas, tests, or records affected by the change.
- **Stale-reference sweep:** search active code, configuration, and documentation for removed or renamed identifiers.
- **Authoritative record:** update the owning fact source; do not create a competing mutable copy.
- **Leftovers:** list any unresolved decision or external/manual step.

## Success signal

A reviewer can see the fresh checks, affected surfaces, stale-reference result, and intentional leftovers without reading a general risk essay.