Cursor Code Review (Superpowers)
@obraSuperpowers' requesting-code-review skill: the agent sends a git diff to a reviewer subagent and gets Critical/Important/Minor findings and a verdict.
Instruction-only: two Markdown files, no scripts, no network, no keys; the reviewer is told to stay read-only on your checkout.
Install Cursor Code Review (Superpowers) in Google Antigravity
Antigravity loads skills from .agents/skills/ in your project or ~/.gemini/config/skills/ for all projects (official docs). Full guide
Install the "Cursor Code Review (Superpowers)" skill for Google Antigravity. Follow the steps at https://www.antigravityskills.org/install/cursor-code-review-pro.md (source: https://github.com/obra/superpowers/tree/main/skills/requesting-code-review). Before running anything, show me what you will download and whether it includes scripts, and wait for my OK. Install it into this project (.agents/skills/) unless I say global. When done, check that Antigravity lists it as an installed skill.
The agent reads the install file, shows you what it will download and waits for your OK.
Option 2: install it yourself
- 1. Option A: install the whole plugin with the Antigravity CLI
agy plugin install https://github.com/obra/superpowers
This is the command in the Superpowers README (Antigravity section). It installs all 15 Superpowers skills, including requesting-code-review. We did not run it.
- 2. Option B: clone and copy only this skill
git clone --depth 1 https://github.com/obra/superpowers /tmp/superpowers
Download the repository to a temporary folder.
- 3. Copy it into your workspace
mkdir -p .agents/skills && cp -r /tmp/superpowers/skills/requesting-code-review .agents/skills/
Run this from your project root. Antigravity reads workspace skills from <project>/.agents/skills/<folder>/, so you should end up with .agents/skills/requesting-code-review/SKILL.md and code-reviewer.md.
- 4. Or install it globally
mkdir -p ~/.gemini/config/skills && cp -r /tmp/superpowers/skills/requesting-code-review ~/.gemini/config/skills/
Use this instead of the workspace copy to make the skill available in every project. Optionally copy skills/receiving-code-review as well.
- 5. Check that Antigravity sees it
Ask "What skills do you have?" (Antigravity 2.0 app has no /skills command). Antigravity CLI: run /skills; in a session that was already open, run /skills reload first. Look for requesting-code-review.
No API keys; needs git. Option A installs every Superpowers skill and changes how the agent works (skills trigger on their own); Option B adds just this one.
Using Claude Code, Cursor or Codex? See other assistants below.
What is Cursor Code Review (Superpowers)?
How to use Cursor Code Review (Superpowers)?
Key features of Cursor Code Review (Superpowers)
- ✓We counted at b739a8a (repo HEAD, 2026-10-20): the skill folder has 2 files, SKILL.md (95 lines, 2,974 bytes) and code-reviewer.md (198 lines, 6,449 bytes), and no scripts. git diff shows the folder is identical to bb92a77, the commit of our earlier review.
- ✓We counted: SKILL.md has 4 placeholders ({DESCRIPTION}, {PLAN_OR_REQUIREMENTS}, {BASE_SHA}, {HEAD_SHA}) and the reviewer template checks 5 areas: plan alignment, code quality, architecture, testing and production readiness.
- ✓The template (code-reviewer.md) makes the reviewer read-only on your checkout, forbids it from spawning subagents of its own, and asks it to list every behaviour it set aside in a "Declined to judge" section before the verdict.
- ✓Output format fixed by the template: Strengths, Issues grouped Critical (Must Fix) / Important (Should Fix) / Minor (Nice to Have) with file:line, Recommendations, then "Ready to merge? Yes | No | With fixes" with a 1-2 sentence reason.
- ✓We counted: the repo has 15 skills in skills/ and 237 tracked files. executing-plans and subagent-driven-development both point at this same code-reviewer.md template, and receiving-code-review covers the other side (how to act on feedback).
- ✓README documents Antigravity: `agy plugin install https://github.com/obra/superpowers` (reinstall the same command to update). The repo ships a native .antigravity-plugin/plugin.json (version 7.0.0), and its own design doc (docs/superpowers/specs/2026-10-06-antigravity-marketplace-design.md) says that with this manifest agy finds all 15 skills and skips the Claude-format hook file, because agy has no SessionStart event.
When to use Cursor Code Review (Superpowers)
- 1Review your own changes before merging to main
- 2Check each task in a multi-step plan before moving to the next
- 3Get a fresh-eyes review when you are stuck on a bug
- 4Take a baseline review before a refactor
Installation & Setup Guide
Agent Rules / Prompt SetupFollow these steps (taken from the project's own docs) to configure Cursor Code Review (Superpowers) in your development environment.
/add-plugin superpowers
Run in Cursor Agent chat, or search for "superpowers" in the plugin marketplace (README).
/plugin install superpowers@claude-plugins-official
From Anthropic's official marketplace; alternatively `/plugin marketplace add obra/superpowers-marketplace` then `/plugin install superpowers@superpowers-marketplace` (README).
agy plugin install https://github.com/obra/superpowers
Installs all Superpowers skills (README). Per the repo design doc, agy skips the Claude-format session-start hook.
gemini extensions install https://github.com/obra/superpowers
Update later with `gemini extensions update superpowers` (README).
Usage Example & Verification
1) SKILL.md example: "[Just completed Task 2: Add verification function] You: Let me request code review before proceeding." The agent dispatches the reviewer with DESCRIPTION, PLAN_OR_REQUIREMENTS, BASE_SHA and HEAD_SHA. 2) Our example: "I finished the payment retry feature on this branch. Request a code review against docs/plans/retry.md, using the merge base with origin/main." -> The agent takes BASE_SHA from git merge-base origin/main HEAD (the command SKILL.md suggests), HEAD_SHA from git rev-parse HEAD, and returns severity-grouped findings with file:line. 3) Our example: "Review only my last commit before I push." -> BASE_SHA = HEAD~1, as in the SKILL.md snippet; the reviewer sees just that diff.
Security Review
Static reviewInstruction-only: two Markdown files, no scripts, no network, no keys; the reviewer is told to stay read-only on your checkout.
Full review: scope, findings, risks
skills/requesting-code-review/ contains SKILL.md and code-reviewer.md, both Markdown with no scripts. The commands it tells the agent to run are git rev-parse, git log and git diff to build the review range; code-reviewer.md tells the reviewer to stay read-only on the checkout and use a separate `git worktree add /tmp/review-<SHA>` if it needs another revision. The reviewer is told not to spawn further subagents. There are no HTTP calls, environment variables or API keys in the skill. When installed as a plugin, hooks/hooks.json (Claude Code) and hooks/hooks-cursor.json (Cursor) run hooks/session-start, a bash script that reads skills/using-superpowers/SKILL.md, escapes it and prints it as additional session context; a grep found no curl, wget or eval in it. For Antigravity the repo ships .antigravity-plugin/plugin.json and its design doc says agy installs it as a native plugin and skips the hook file. This is a static review; we did not run any of it.
Operational Notes & Known Limitations
Known Limitations
- •Needs a git repository with commits to diff (BASE_SHA..HEAD_SHA).
- •Relies on the agent being able to dispatch a subagent; the template assumes a general-purpose subagent. In Antigravity CLI the repo maps this to invoke_subagent (skills/using-superpowers/references/antigravity-tools.md), a file that is not inside the requesting-code-review folder, so a single-folder copy does not carry it.
- •Reviews against a plan or requirements you provide; with no plan the template tells the reviewer to judge by what a reasonable user would expect.
- •Not a Cursor product feature and not named "Cursor Code Review": it is a portable SKILL.md that Cursor can load through the Superpowers plugin.
- •The full plugin adds all 15 skills that trigger on their own and, in Claude Code and Cursor, a session-start hook; the README also notes an optional, disable-able version ping in brainstorming's visual companion (SUPERPOWERS_DISABLE_TELEMETRY).
Frequently Asked Questions
Is the Code Review skill for Cursor safe?
In our static review of commit b739a8a the skill folder is two Markdown files with no scripts. It tells the agent to run read-only git commands (rev-parse, log, diff, show) and the reviewer must not change the working tree, index, HEAD or branches. The full plugin also adds hooks/session-start for Claude Code and Cursor, a bash script that prints the using-superpowers skill as session context.
How do I install the Code Review skill in Antigravity?
The README documents `agy plugin install https://github.com/obra/superpowers`, which installs all Superpowers skills. To take only this one, clone the repo to /tmp and copy skills/requesting-code-review into .agents/skills/ (or ~/.gemini/config/skills/), then ask "What skills do you have?" (Antigravity CLI: /skills).
How do I use it in Cursor?
Run `/add-plugin superpowers` in Cursor Agent chat (README). The skills then trigger automatically, including requesting-code-review after a task or before merging.
Is this an official Cursor feature?
No. Cursor's own review features are separate. This is a community SKILL.md from obra/superpowers (MIT) that Cursor can load as a plugin; we list it because people searching "cursor code review skill" want a code-review skill to use inside Cursor.
What does the review output look like?
Strengths, Issues grouped as Critical (must fix), Important (should fix) and Minor (nice to have) with file:line, Recommendations, and an Assessment: Ready to merge? Yes, No or With fixes, plus a short reason.
Supported Platforms
Keep exploring this topic
Browse the full Antigravity skills directory for more source-linked skills with install steps and static safety reviews.
Related Skills
Clean Code
@sickn33
A one-file Clean Code playbook (Robert C. Martin's rules on naming, functions, comments, errors, tests and classes) that AI coding agents follow when writing, reviewing or refactoring code.
TDD Workflow
@sickn33
Community skill that makes an agent work test-first: one failing behavioural test, minimal code to pass, then refactor, with a separate guide on mock anti-patterns.
Rust Best Practices
@apollographql
Apollo GraphQL's rust-best-practices skill: makes your agent write and review Rust by Apollo's handbook (ownership, errors, Clippy, tests, generics).
Popular Skills
View All →Agent Manager
@sickn33
Manage multiple local CLI agents via tmux sessions.
Systematic Debugging
@sickn33
Debug systematically, not randomly. Find and fix bugs methodically.
Browser Automation (Playwright)
@sickn33
Expert browser automation for cleaning scraping and reliable testing.