Agent skill

Review This Branch

by no-human-ai in no-human-ai/no_human

Run the nohuman review gate (fresh-session adversarial reviewer + tamper guard) over the current branch or a GitHub pull request, with no server, no database, and no onboarding, and relay the…

MITAuto-check passedDevelopment

Install Review This Branch

skills CLI
$ npx skills add no-human-ai/no_human --skill review-this-branch -a claude-code

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

GitHub CLI
$ gh skill install no-human-ai/no_human review-this-branch --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/no-human-ai/no_human.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/no-human/skills/review-this-branch .claude/skills/review-this-branch && 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
review-this-branch
GitHub stars
324
Token cost
~1.4k tokens
SKILL.md length
835 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

Run the nohuman review gate (fresh-session adversarial reviewer + tamper guard) over the current branch or a GitHub pull request, with no server, no database, and no onboarding, and relay the…

  • Tasks that involve Human-in-the-loop approvals
  • SKILL.md covers When to use, Prerequisite: your own Claude…, Running it and Reading the result: the…, plus 1 more section
  • Calls git and claude
  • Tasks that involve Pull requests

What it does

Review This Branch is an agent skill from no-human-ai/no_human. Run the nohuman review gate (fresh-session adversarial reviewer + tamper guard) over the current branch or a GitHub pull request, with no server, no database, and no onboarding, and relay the pass/fail checklist.

Its SKILL.md is about 1.4k 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, covering Human-in-the-loop approvals and Pull requests. It works with GitHub and Model Context Protocol. The repository describes itself as: From ticket to reviewed pull request. Free and open-source, on your machine. The licence is MIT.

When your agent uses it

  • Tasks that involve Human-in-the-loop approvals
  • Tasks that involve Pull requests

Example prompts

  • “/review-this-branch”

What it can do on your machine

Read from SKILL.md and the folder at commit cdcbd0a. 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
    • claude

    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

Review This Branch loads about 1.4k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 835 words of instructions outside code blocks.

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

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 no-human-ai/no_human at commit cdcbd0a, republished under its MIT licence (© no-human-ai). 835 words, ~1,439 tokens.

Download SKILL.mdSave it as .claude/skills/review-this-branch/SKILL.md (or your agent's skills folder).
name
review-this-branch
description
Run the no_human review gate (fresh-session adversarial reviewer + tamper guard) over the current branch or a GitHub pull request, with no server, no database, and no onboarding, and relay the pass/fail checklist.

Review this branch

Run nh gate to get a fresh-session, adversarial code review and a test-tampering check over a diff, right now, with nothing installed or running beyond the nh CLI itself.

When to use

  • Someone asks "review this branch" / "check this PR" / "is this safe to merge" and wants a real second-model review with file:line citations, not a summary you write yourself.
  • There is no no_human server running and no ~/.no_human database set up. Unlike file-a-task, this skill needs neither. It runs once and exits.

Prerequisite: your own Claude credential

nh gate uses your own Claude credential, the same one every other nh command uses, never one belonging to no_human itself. If none is on file, create it with:

bash
claude setup-token

nh gate also needs the nh CLI on PATH and a claude CLI it can find: the one bundled inside the installed SDK package is used first, so a separate install on PATH is not required. If either precondition is missing, the command refuses and names exactly what is missing. It never prints a pass when it could not actually run.

Running it

Two invocations, both read-only:

bash
nh gate                        # current branch vs. its merge base with origin's default branch
nh gate --pr <github-pr-url>   # a GitHub pull request's head vs. its merge base

Optional flags: --repo <path> to point at a checkout other than the current directory, --base <ref> to override the comparison base.

The comparison actually used, for example working tree branch ... against merge base with origin/<default> or pull request owner/repo#N head ... against merge base with origin/<default>, is always printed at the top of the output. If the working tree has uncommitted changes, the output says so explicitly and those files are not reviewed; commit them first if they should be.

Reading the result: the exit-code contract

Exit codeMeaning
0Gate passed: reviewer found no blocking findings and the tamper guard found no test-weakening.
1Gate failed: a blocking review finding or a tamper-guard finding (deleted/weakened tests).
2Gate refused to run: no review verdict was reached at all. A named precondition failed: no credential, no upstream, not a git repo, PR fetch failed, the diff is over the single-turn review cap, or the reviewer timed out / hit a transport error.

On exit 2, never report a pass. Also never report the reviewer's checklist as a fail, since the reviewer never actually finished. This includes a diff too large to review and a reviewer timeout or transport error: both refuse before or without a real verdict, not with a "no findings" pass or a "timeout" finding treated as a real blocking issue. Relay the exact refusal message back to the human (it names the missing credential, missing upstream, oversized diff, or fetch/transport failure) instead of guessing at a verdict. Only exit 0 is a pass; treat exit 1 and exit 2 identically as "cannot say this is fine" until the human has read the printed detail.

Relay the full Markdown checklist nh gate prints back to the human, including every file:line citation and the tamper guard's before/after counts. Do not summarize away the citations or the counts.

Show full SKILL.md (342 more words)Show less

Product boundary: read and report only, never write

This skill only reads and reports. It never commits, pushes, merges, or edits a tracked file in your checkout, and it must never be followed by a commit, a push, an approval, or a merge of the pull request on the agent's behalf. The exact write surface, stated in full:

  • ~/.no_human/config.yaml is read if it already exists (for reviewer backend/model settings); it is never created by this skill, and there is no on-demand ~/.no_human setup here, unlike other nh commands. One thing does write there: the CLI's background update check caches its result in ~/.no_human/cache/update-check.json, creating that directory if the run lasts long enough to finish the check. Nothing else in ~/.no_human is created or modified.
  • In --pr mode only, one additive git fetch of the pull request's ref writes FETCH_HEAD and the fetched objects into your checkout. It creates no branch and moves no ref you own.
  • Every invocation, default and --pr alike, also makes one local git clone --local --shared of your own checkout into a throwaway temp directory (see below) and a git checkout inside that temp directory only, never against your own checkout.

Beyond that, nh gate only runs read-only git plumbing against your checkout: rev-parse, merge-base, diff, status --porcelain, symbolic-ref (reads the locally recorded default branch; never a network call), and config --get remote.origin.url (to check a --pr URL names your own repo). It also uses the tamper guard's own read-only calls (ls-tree, show) and a read-only reviewer backend. This list describes what the current implementation does, not a promise that it will never grow; it never becomes a write against a tracked file.

The throwaway clone exists so the review reads the exact committed tree it diffed instead of your live working tree (which may be dirty) or, in PR mode, whatever branch you happen to have checked out; it is deleted before the command exits. Merge is always the human's action. After running this skill, your job is to relay the checklist, not to act on it.

© no-human-ai, MIT. 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 plugins/no-human/skills/review-this-branch of no-human-ai/no_human.

Open the folder on GitHubat commit cdcbd0a

Compare with similar skills

Review This Branch 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.

Review This Branch compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review This Branch this skillno-human-ai/no_human324—~1.4kAutomated safety check: PassMIT
Project Pull Requestswimmwatch/cloakbrowser-mcp164—~1kAutomated safety check: PassMIT
Plannotator Referencebacknotprop/plannotator9.3k—~6.8kAutomated safety check: WarnApache-2.0
GitHub Commentingjuspay/neurolink148—~698Automated safety check: PassMIT
Agent Swarm PRruvnet/ruflo74k2 repos~2.8kAutomated safety check: PassMIT
Plane Release Notes Generatormakeplane/plane61k—~2.5kAutomated safety check: PassAGPL-3.0

Similar skills

  • Project Pull Request

    swimmwatch/cloakbrowser-mcp

    Create, update, prepare, or review a cloakbrowser-mcp GitHub Pull Request only when the user explicitly requests PR work.

    164 GitHub stars~1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Plannotator Reference

    backnotprop/plannotator

    Reference for picking the right Plannotator tool or command for plan review, code review, annotating files and URLs, archived plan decisions and Guided Reviews.

    9.3k GitHub stars~6.8k tokensUpdated today
    DevelopmentAuto-check: warnings
  • GitHub Commenting

    juspay/neurolink

    How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules.

    148 GitHub stars~698 tokensUpdated today
    DevelopmentAuto-check passed
  • Agent Swarm PR

    ruvnet/ruflo

    Agent skill for swarm-pr - invoke with $agent-swarm-pr. An agent skill from ruvnet/ruflo.

    74k GitHub starsUsed in 2 repos~2.8k tokens
    DevelopmentAuto-check passed
  • Builds categorized release notes for a Plane release pull request from its commits and writes them into the PR description, for both the plane-cloud and plane-ee repos.

    61k GitHub stars~2.5k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Mariadb Operator PR Review

    mariadb-operator/mariadb-operator

    Perform a structured maintainer-style PR review for the mariadb-operator repository.

    1k GitHub stars~3.3k tokensUpdated 4 days ago
    DevelopmentAuto-check passed

More from no-human-ai/no_human

  • File A Task

    no-human-ai/no_human

    File work into nohuman (taskadd) and check on it (taskstatus) via the nohuman MCP bridge, instead of doing the work inline.

    324 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed
  • Release Notes

    no-human-ai/no_human

    Write release notes for a tagged release — a business-impact summary of what changed for the user, plus a thanks section naming every contributor whose commits are in the release.

    324 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

Questions about Review This Branch

What does Review This Branch do?

Run the nohuman review gate (fresh-session adversarial reviewer + tamper guard) over the current branch or a GitHub pull request, with no server, no database, and no onboarding, and relay the…. Review This Branch is an agent skill from no-human-ai/no_human. Run the nohuman review gate (fresh-session adversarial reviewer + tamper guard) over the current branch or a GitHub pull request, with no server, no database, and no onboarding, and relay the pass/fail checklist.

When should I use Review This Branch?

Review This Branch fits situations like: tasks that involve Human-in-the-loop approvals; tasks that involve Pull requests.

How do I install Review This Branch in Claude Code?

Run `npx skills add no-human-ai/no_human --skill review-this-branch -a claude-code`. Or copy the skill folder (plugins/no-human/skills/review-this-branch in no-human-ai/no_human) into .claude/skills/review-this-branch in your project. Claude Code loads it when a task matches its description.

How do I install Review This Branch in Codex?

Run `npx skills add no-human-ai/no_human --skill review-this-branch -a codex`. Or copy the skill folder (plugins/no-human/skills/review-this-branch in no-human-ai/no_human) into .agents/skills/review-this-branch in your project. Codex loads it when a task matches its description.

Can I use Review This Branch 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 no-human-ai/no_human --skill review-this-branch -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-this-branch, .gemini/skills/review-this-branch, .github/skills/review-this-branch and .opencode/skills/review-this-branch in your project.

What does Review This Branch need to run?

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

Does Review This Branch 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 Review This Branch 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 Review This Branch use?

Review This Branch is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Review This Branch use?

About 1.4k tokens (SKILL.md is roughly 5.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 Review This Branch?

Skills that share tags, products or a category with Review This Branch: Project Pull Request (swimmwatch/cloakbrowser-mcp, 164 stars), Plannotator Reference (backnotprop/plannotator, 9.3k stars), GitHub Commenting (juspay/neurolink, 148 stars) and Agent Swarm PR (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review This Branch?

no-human-ai (a GitHub organization) maintains it in no-human-ai/no_human, which has 324 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 9, 2026.

Source: no-human-ai/no_human on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.