Finishing a Development Branch
obra/superpowers
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.
A skill your agent uses for focused review of a Neva pull request, branch, diff, or patch.
Install Review
$ npx skills add nevalang/neva --skill review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nevalang/neva review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nevalang/neva.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/review .claude/skills/review && rm -rf skills-srcUse ~/.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/
Install the "review" agent skill from https://github.com/nevalang/neva/tree/main/.codex/skills/review into .claude/skills/review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nevalang/neva/tree/main/.codex/skills/reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nevalang/neva --skill review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nevalang/neva review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nevalang/neva.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/review .agents/skills/review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "review" agent skill from https://github.com/nevalang/neva/tree/main/.codex/skills/review into .agents/skills/review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nevalang/neva --skill review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nevalang/neva review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nevalang/neva.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/review .cursor/skills/review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "review" agent skill from https://github.com/nevalang/neva/tree/main/.codex/skills/review into .cursor/skills/review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nevalang/neva.git --path .codex/skills/review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nevalang/neva --skill review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nevalang/neva review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nevalang/neva.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/review .gemini/skills/review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "review" agent skill from https://github.com/nevalang/neva/tree/main/.codex/skills/review into .gemini/skills/review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nevalang/neva reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nevalang/neva --skill review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nevalang/neva.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/review .github/skills/review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "review" agent skill from https://github.com/nevalang/neva/tree/main/.codex/skills/review into .github/skills/review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nevalang/neva --skill review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nevalang/neva review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nevalang/neva.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/review .opencode/skills/review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "review" agent skill from https://github.com/nevalang/neva/tree/main/.codex/skills/review into .opencode/skills/review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
review- GitHub stars
- 1.1k
- Token cost
- ~382 tokens
- SKILL.md length
- 182 words
- Files
- 5 (incl. references)
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses for focused review of a Neva pull request, branch, diff, or patch.
- Works in 5 steps: Read the diff and required repository… → Select the focused perspectives that… → Choose whether to use subagents based on… → …
- Focused review of a Neva pull request
- SKILL.md covers Workflow and Output Contract
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Review is an agent skill from nevalang/neva. Use for focused review of a Neva pull request, branch, diff, or patch.
Its SKILL.md is about 380 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/review-correctness.md`, `references/review-performance.md` and `references/review-readability.md`).
It sits in Development, covering Pull requests. The repository describes itself as: Dataflow programming language where you write a program as a message-passing graph and everything runs in parallel by default. It has strong static types, compiles to machine… The licence is MIT.
When your agent uses it
- Focused review of a Neva pull request
- Tasks that involve Pull requests
Example prompts
- “/review”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Read the diff and required repository context
- Select the focused perspectives that match the change and its risk
- Choose whether to use subagents based on the change's size and risk. For a
- Deduplicate overlapping findings.
- Output only actionable findings and blocking questions. If there are no
What it can do on your machine
Read from SKILL.md and the folder at commit 127afd9. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 loads about 382 tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 19 tokens; SKILL.md has 182 words of instructions outside code blocks.
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 nevalang/neva at commit 127afd9, republished under its MIT licence (© nevalang). 182 words, ~382 tokens.
Download SKILL.mdSave it as
.claude/skills/review/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- review
- description
- Use for focused review of a Neva pull request, branch, diff, or patch.
Review
Use this skill for high-signal review of a code change. The change may be a pull request, a branch, a local diff, or a patch. The goal is to publish only required changes or blocking questions.
Workflow
- Read the diff and required repository context:
AGENTS.md- canonical documentation named by its change-routing table
- Select the focused perspectives that match the change and its risk:
- correctness:
references/review-correctness.md - style and readability:
docs/user/style_guide.mdfor Neva code, plusreferences/review-readability.md - performance:
references/review-performance.md - security:
references/review-security.md
- correctness:
- Choose whether to use subagents based on the change's size and risk. For a small, focused diff, review directly; for a broad or high-risk diff, split the selected perspectives into focused passes with task-specific prompts.
- Deduplicate overlapping findings.
- Output only actionable findings and blocking questions. If there are no meaningful findings, say that clearly.
Output Contract
- Findings first, ordered by severity.
- Include file/line references whenever possible.
- Keep the output proportionate to the findings; do not impose a template when there is no meaningful feedback.
- Report clear violations of
docs/user/style_guide.mdfor Neva code. Do not report subjective style preferences.
© nevalang, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in .codex/skills/review of nevalang/neva.
- SKILL.md
- references/review-correctness.md
- references/review-performance.md
- references/review-readability.md
- references/review-security.md
Open the folder on GitHubat commit 127afd9
Compare with similar skills
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Review this skillnevalang/neva | 1.1k | — | ~382 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence |
Similar skills
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.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
Record PR Demo
payloadcms/payload
A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.
More from nevalang/neva
All 8 skills in this repoNeva To Mermaid
nevalang/neva
Convert Neva programs to valid Mermaid flowchart diagrams. An agent skill from nevalang/neva.
Release Neva
nevalang/neva
Prepare a Neva GitHub release draft from merged PRs, previous release style, and local multi-platform artifacts.
Release Discord Post
nevalang/neva
Create a Discord-ready Neva release announcement from a GitHub release payload.
Release Telegram Post
nevalang/neva
Create a Telegram-ready Neva release announcement from a GitHub release payload.
Papercut
nevalang/neva
Capture or triage small Neva repository and engineering-harness frictions without derailing feature work.
Go
nevalang/neva
A skill your agent uses for Go changes in Neva: authoring, refactoring, debugging, or review.
Related
Categories
Questions about Review
What does Review do?
A skill your agent uses for focused review of a Neva pull request, branch, diff, or patch. Review is an agent skill from nevalang/neva. Use for focused review of a Neva pull request, branch, diff, or patch.
When should I use Review?
Review fits situations like: focused review of a Neva pull request; tasks that involve Pull requests.
How do I install Review in Claude Code?
Run `npx skills add nevalang/neva --skill review -a claude-code`. Or copy the skill folder (.codex/skills/review in nevalang/neva) into .claude/skills/review in your project. Claude Code loads it when a task matches its description.
How do I install Review in Codex?
Run `npx skills add nevalang/neva --skill review -a codex`. Or copy the skill folder (.codex/skills/review in nevalang/neva) into .agents/skills/review in your project. Codex loads it when a task matches its description.
Can I use 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 nevalang/neva --skill 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/review, .gemini/skills/review, .github/skills/review and .opencode/skills/review in your project.
What does Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Review is instructions for the agent only.
Does Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is 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 Review use?
Review 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 use?
About 382 tokens (SKILL.md is roughly 1.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.
What are the alternatives to Review?
Skills that share tags, products or a category with Review: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 90k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Review?
nevalang (a GitHub organization) maintains it in nevalang/neva, which has 1,085 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on August 23, 2026.
Source: nevalang/neva on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.