Official agent skill

Closeout Review

by trailofbits in trailofbits/coop

Run the final scope-controlled review before committing, pushing, or opening a PR.

OfficialApache-2.0Auto-check passedDevelopment

Install Closeout Review

skills CLI
$ npx skills add trailofbits/coop --skill closeout-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install trailofbits/coop closeout-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/trailofbits/coop.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/closeout-review .claude/skills/closeout-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
closeout-review
GitHub stars
767
Token cost
~700 tokens
SKILL.md length
321 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

Run the final scope-controlled review before committing, pushing, or opening a PR.

  • Closeout review
  • SKILL.md covers Freeze scope first, Classify every validated finding and Converge
  • Calls git
  • Readiness checks

What it does

Closeout Review is an agent skill from trailofbits/coop, published by the product's own GitHub organization. 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.

Its SKILL.md is about 700 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. The repository describes itself as: Isolated VM environment for running Claude Code and Codex. The licence is Apache-2.0.

When your agent uses it

  • Closeout review
  • Readiness checks
  • Self-review of a completed branch

Example prompts

  • “/closeout-review”

What it can do on your machine

Read from SKILL.md and the folder at commit 4929257. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Closeout Review loads about 700 tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 321 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~45
When it runs · the whole SKILL.md, loaded when a task matches
~700

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from trailofbits/coop at commit 4929257, republished under its Apache-2.0 licence (© trailofbits). 321 words, ~700 tokens.

Download SKILL.mdSave it as .claude/skills/closeout-review/SKILL.md (or your agent's skills folder).
name
closeout-review
description
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.

Closeout 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.

For changes to platform #[cfg] gates, backend aliases, or platform-only types/call paths, run check and clippy for every affected OS, natively or with an available cross target. Verify the ordinary non-test library build as well as tests: --all-targets does not select other operating systems, and cfg(test) can hide unused production variants. Report unavailable targets as unrun platform gates.

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:

bash
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.

© trailofbits, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/closeout-review of trailofbits/coop.

Open the folder on GitHubat commit 4929257

Compare with similar skills

Closeout Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Closeout Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Closeout Review this skilltrailofbits/coop767—~700Automated safety check: PassApache-2.0
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed
  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from trailofbits/coop

  • Review

    trailofbits/coop

    Official

    Review a coop pull request or local diff with independent, self-validated correctness, design, convention, security, API, test, documentation, and comment lenses.

    767 GitHub stars~3.1k tokensUpdated today
    Auto-check passed
  • Babysit PR

    trailofbits/coop

    Official

    Shepherd the current user's open PR through base updates, CI failures, and review feedback without rewriting history or merging.

    767 GitHub stars~625 tokensUpdated today
    Auto-check passed
  • Babysit My PRs

    trailofbits/coop

    Official

    Triage and shepherd all open PRs owned by the current GitHub user, isolating each writable worker in its own worktree.

    767 GitHub stars~453 tokensUpdated today
    Auto-check passed
  • Integration

    trailofbits/coop

    Official

    Run and interpret coop's VM integration suite locally on Lima or remotely on Firecracker.

    767 GitHub stars~227 tokensUpdated today
    Auto-check passed
  • Mutation Check

    trailofbits/coop

    Official

    Run cargo-mutants for changed coop logic and keep .cargo/mutants.toml synchronized.

    767 GitHub stars~389 tokensUpdated today
    Auto-check passed

Categories

Questions about Closeout Review

What does Closeout Review do?

Run the final scope-controlled review before committing, pushing, or opening a PR. Closeout Review is an agent skill from trailofbits/coop, published by the product's own GitHub organization. Run the final scope-controlled review before committing, pushing, or opening a PR.

When should I use Closeout Review?

Closeout Review fits situations like: closeout review; readiness checks; self-review of a completed branch.

How do I install Closeout Review in Claude Code?

Run `npx skills add trailofbits/coop --skill closeout-review -a claude-code`. Or copy the skill folder (.agents/skills/closeout-review in trailofbits/coop) into .claude/skills/closeout-review in your project. Claude Code loads it when a task matches its description.

How do I install Closeout Review in Codex?

Run `npx skills add trailofbits/coop --skill closeout-review -a codex`. Or copy the skill folder (.agents/skills/closeout-review in trailofbits/coop) into .agents/skills/closeout-review in your project. Codex loads it when a task matches its description.

Can I use Closeout Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add trailofbits/coop --skill closeout-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/closeout-review, .gemini/skills/closeout-review, .github/skills/closeout-review and .opencode/skills/closeout-review in your project.

What does Closeout Review need to run?

Going by SKILL.md and its folder, Closeout Review needs the command-line tools its instructions call (git).

Does Closeout Review access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Closeout Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Closeout Review use?

Closeout Review is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Closeout Review use?

About 700 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Closeout Review?

Skills that share tags, products or a category with Closeout Review: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Closeout Review?

trailofbits (a GitHub organization, an official publisher) maintains it in trailofbits/coop, which has 767 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 9, 2026.

Source: trailofbits/coop on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.