super-review · v3.35.0 · 2026-11-15 · sha256 c64e1433147f4c0b

super-review v3.35.0A

Immutable. This exact content never changes and is served at /api/v1/blob/c64e1433147f4c0b.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_uichbgu2mrpjtcxk/c64e1433147f4c0b22e735a9e55aaa48125fb96589732020947be56e049b5715.json

Then /plugin install super-review@markdownregistry-uichbgu2mrpjtcxk in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: super-review
description: "Explicit Super Review of Go, TypeScript, Rust, or Java PRs or local source for readability and maintainability, or help using that review."
disable-model-invocation: true
metadata:
  version: "3.35.0"
---

# Super Review

**Clarity.** Recommend source-supported improvements to expression and structure,
local or structural, and retain code when changing it offers no supported benefit.
Understand behavior as context for advice without claiming tested equivalence.
The review reads only: never edit reviewed source, post comments, or run project
code, tests, builds, linters, hooks, or installers. Bugs, security, test
coverage, and business requirements belong to separate reviews.

## Start or explain

For help, explain usage and stop without acquiring source or spawning specialists.
For a review with no identifiable target in the request or active context, ask
only for that target; reuse a supplied PR, local changes, or an explicit
whole-project target without asking again, and accept file and lens scope in
ordinary language.

Orchestrate through the active adapter: [Codex](references/harnesses/codex.md),
[Claude Code](references/harnesses/claude.md), [Cursor](references/harnesses/cursor.md),
[Antigravity](references/harnesses/antigravity.md),
or the installed OpenCode role. When the user explicitly asks to run specialists
in another installed harness, launch them there through
[external specialists](references/harnesses/external.md).

## Review and deliver

Follow [the contract](references/review-contract.md) and
[workflow](references/workflow.md) for source pinning, team policy,
[language](references/languages.md) and aspect selection, neutral task packets,
and completion. Keep all eight base questions unless the user narrows scope;
profiles deepen their owner lens. Give each fresh specialist one lens, or a
related pair only when the user explicitly asks for a compact review of a small
change.

Decide every candidate and what the code becomes with
[verification](references/verification.md), then deliver the complete report
using [the report structure](assets/report-template.md) in the harness or a
permitted artifact outside the reviewed tree.