Closeout Review
SkillDev toolsLets your agent run a final self-review of a finished branch before you commit, push, or open a pull request.
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the Closeout Review skill
About this skill
Run the final scope-controlled review before committing, pushing, or opening a PR. Use for closeout review, readiness checks, or self-review of a completed branch.
What this skill tells your AI
The instructions your AI receives, as published by trailofbits/coop in .agents/skills/closeout-review/SKILL.md and read by ahel’s review.
This is the final gate for a non-trivial change. Read and apply the repository
review skill, then resolve its findings locally. Do not
post review comments.
Freeze scope first
Before reading findings, record the original request, owner/module boundary, changed files, and non-generated LOC against the base. This is the baseline; review must not silently redefine the task.
Classify every validated finding
- In-scope blocker: introduced by this diff, same owner boundary, and fixable without reframing the task. Fix now.
- Follow-up: real but adjacent, optional, or a separate cleanup/bug class. Record it; do not absorb it.
- Stop and escalate: requires a new contract, protocol, storage/API change, security confirmation, or product/design decision. Ask the user.
When uncertain between blocker and follow-up, use follow-up. Findings are hypotheses: independently verify them before changing code.
Converge
Apply only in-scope blockers. Run the narrow test for each fix, then format,
clippy with -D warnings, and the applicable broader tests. Use the
mutation-check skill for scoped logic and the
integration skill for guest-visible/lifecycle
changes. Re-run the review skill against the complete updated diff, not only the
last fix commit.
Stop after two non-converging review/fix cycles, if the diff grows beyond about twice the baseline without approval, or when a local fix has become a redesign.
Report what ran, accepted/fixed findings, rejected findings with a one-line
reason, follow-ups, unrun platform gates, and a clean or blocked verdict.
On a clean verdict, record the reviewed commit for the compatibility PR gate:
COMMON_DIR="$(git rev-parse --git-common-dir)"
case "$COMMON_DIR" in /*) ;; *) COMMON_DIR="$PWD/$COMMON_DIR" ;; esac
COMMON_DIR="$(cd "$COMMON_DIR" && pwd)"
DIR="$COMMON_DIR/closeout-review"
mkdir -p "$DIR"
git rev-parse HEAD > "$DIR/$(git rev-parse --abbrev-ref HEAD | tr '/' '-')"
The marker is valid only for the current commit. Never record it for a blocked verdict or to bypass review.
Signals
- GitHub stars
- 740
- Forks
- 38
- Last commit
- Oct 2026
Advanced
- Item type
- skill
- Key
closeout-review- Source
- github.com/trailofbits/coop