# Review Change Stack

> Review a dependent branch or pull-request stack in dependency order with one receipt per change and a stack-level verdict.

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

---


# Review a change stack

Read [the execution contract](references/contract.json) before starting. Validate the final receipt with its parameterized `verification.argv`, replacing `{python}`, `{skill_dir}`, and `{receipt}` with concrete local values.

Resolve the actual base and dependency order first. For each change, inspect
its diff against the immediate parent, run the relevant proof, and record
correctness, security, migration, test, and rollback findings.

Do not let a green child hide a broken parent. Mark each item `PASS`, `REVISE`,
or `BLOCKED`, then check cross-change contracts and produce one stack verdict.
If an optional stack CLI is unavailable, use Git ancestry and label provider
metadata `UNVERIFIED` instead of inventing it.