Skip to content
Skills Library
Programming · Review & audit

review-gate

/review-gate

Use before an agent-produced diff is committed, pushed, opened as a PR, merged, landed, or applied to user files when explicit implementation approval is missing. Trigger for review gate, review pack, approve before landing, diff first then land, human approval, merge gate, commit gate, push gate, or PR readiness. Produces a concise review pack, records risks and verification, and blocks landing until a human explicitly approves or approves with required fixes.

Repository
spellbook ↗
Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use before an agent-produced diff is committed, pushed, opened as a PR, merged, landed, or applied to user files when explicit implementation approval is missing. Trigger for review gate, review pack, approve before landing, diff first then land, human approval, merge gate, commit gate, push gate, or PR readiness. Produces a concise review pack, records risks and verification, and blocks landing until a human explicitly approves or approves with required fixes.

Original author description

Use before an agent-produced diff is committed, pushed, opened as a PR, merged, landed, or applied to user files when explicit implementation approval is missing. Trigger for review gate, review pack, approve before landing, diff first then land, human approval, merge gate, commit gate, push gate, or PR readiness. Produces a concise review pack, records risks and verification, and blocks landing until a human explicitly approves or approves with required fixes.

How it works

  1. When To Run
  2. Operating Contract
  3. Gate States
  4. Gotchas
  5. Review Pack
  6. Decision Rules
  7. Integration Points
  8. Verification
Original SKILL.md headings · 118 lines, 604 words
SKILL.md preview
---
name: review-gate
description: "Use before an agent-produced diff is committed, pushed, opened as a PR, merged, landed, or applied to user files when explicit implementation approval is missing. Trigger for review gate, review pack, approve before landing, diff first then land, human approval, merge gate, commit gate, push gate, or PR readiness. Produces a concise review pack, records risks and verification, and blocks landing until a human explicitly approves or approves with required fixes."
---

# Review Gate

Use this skill as the last-mile safety checkpoint for agent-generated changes.
It complements PR review tools; it does not replace code review, CI, or human
approval.

Use `assets/review-pack-template.md` when the user needs a reusable review pack
shape.

## When To Run

Run before any of these actions when an agent-generated diff is involved:

- commit
- push
- open or update a PR
- merge or land
- apply a generated patch to user files when the user has not already approved
  that exact implementation path

Read-only review, planning, issue triage, and local exploration do not require
this gate unless the next step would land or publish changes.

## Operating Contract

- Direct actions: inspect diffs, collect verification evidence, and draft the
  review pack.
- Escalate before: commit, push, PR creation, merge, branch deletion, or
  applying a generated patch when the user has not approved that exact action.
- Evidence-backed pushback: block landing when verification is stale, sensitive
  surfaces lack review, or approval is ambiguous.
- Feedback loop: convert repeated review findings into new checklist items,
  verification commands, or Review Pack risk prompts.

## Gate States

| State | Meaning | Allowed next action |
| --- | --- | --- |
| `draft_pack` | Review pack is being assembled. | Inspect diff and verification only. |
| `needs_fixes` | Blocking risks or missing evidence exist. | Patch and rerun the gate. |
| `awaiting_human` | Pack is complete but no human approval exists. | Stop before commit, push, PR, merge, or apply. |
| `approved` | Human explicitly approved the pack in the current thread. | Proceed with the named action only. |
| `approved_with_fixes` | Human approved after specific fixes. | Apply fixes, verify, and record evidence before landing. |

Agents must not self-approve. Prior CI success, a reviewer lane, or a green
local test is evidence for the pack, not approval.

## Gotchas

- Approval is action-specific. "Commit it" does not mean "merge it."
- A reviewer lane is independent evidence, not human approval.
- If a fix changes the diff after approval, refresh verification and update the
  pack before landing.

## Review Pack

Produce this compact pack:

```text
review_gate:
- intent:
- diff_summary:
- files_changed:
- driving_skill_or_issue:
- risks:
- missing_tests_or_verification:
- commands_run:
- evidence:
- open_questions:
- approval_needed_for:
- decision:
```

Keep findings ranked by severity. Include exact file paths, PR numbers, issue
numbers, command names, and current head SHA when available.

## Decision Rules

- If verification is stale, missing, or tied to a different head SHA, set
  `needs_fixes`.
- If the diff touches auth, payments, secrets, permissions, `innerHTML`, `eval`,
  shell execution, generated registry, hooks, or high-context files, call that
  out explicitly.
- If user approval is ambiguous, set `awaiting_human` and ask for the named
  action only.
- If the user approves, do exactly the approved action. A commit approval is not
  automatically a merge approval.
- If a required fix changes the diff, rerun the relevant verification and update
  the pack before landing.

## Integration Points

`flowguard` should call this gate at landing checkpoints. Queue skills may use a
reviewer lane for independent findings, but the Review Gate still records the
human-facing pack and approval state.

For GitHub PRs, combine this gate with current remote truth:

- PR head SHA
- check rollup
- merge state
- GraphQL reviewThreads
- linked issue intent

## Verification

For Spellbook changes, the pack usually cites:

```bash
git diff --check
python3 ./scripts/validate_skills.py --check
python3 ./scripts/audit_skill_quality.py skill-name
```

Use project-specific tests for code changes. If a command cannot run, report the
precondition and keep the decision out of `approved`.
Files in this package (2)
  • SKILL.md 4 KB
  • assets/review-pack-template.md 1 KB

Versions

RepositoryScoreLicence
This page · majiayu000/spellbook100MIT
kamiazya/whiteboard100Apache-2.0
Jeff-Kazzee/github-skills100MIT
dperhar/orcestrationmaxxing100MIT
hgbeigi/claude-tools100MIT
draz26648/flutter_craft_skills100MIT
emaballarin/ccplugins90MIT
KerberosClaw/kc_ai_skills90MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 3e14d0d90ef9 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90gate-proposed-change
    Use when asked to evaluate a proposed commit, merge, or auto-merge against a gate config. Not for landing PRs: use gate-and-merge. Read-only.
  • 90pre-landing-review
    Gate-oriented safety audit for code changes before landing, using a checklist with two-pass severity triage. Triggers on: "is this safe to land", "pre-landing review", "safety check before merge", "gate check", "/pre-landing-review". NOT for diff review, use pr-review.
  • 100gate-and-merge
    Use when landing a queue of open PRs: gate each PR, sweep its review feedback to root cause, then merge, repair, hold, or close it. Human-only.
  • 100review
    Pre-landing review of a local diff, branch or PR for concrete defects, scope gaps and landing readiness, ending in SAFE TO LAND, LAND WITH CAUTION or DO NOT LAND. Use for 'review this', 'review my branch', 'is this safe to land' or 'check this diff'. To post comments on a GitHub…
  • 100gate-and-merge
    Use when landing a queue of open PRs: gate each PR, sweep its review feedback to root cause, then merge, repair, hold, or close it. Human-only.
  • 90ship
    Ship a PR through local verification, push, CI, review, and merge without admin override. Use for 'ship', 'ship it', or 'push and merge'. SKIP if the user only wants a PR opened; use create-pr.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.