Agent skill

Plannotator Code Review

by backnotprop in backnotprop/plannotator

Opens Plannotator's browser-based review UI for the current worktree, another directory or a pull request URL, then applies the feedback it returns.

Apache-2.0Auto-check passedDevelopment

Install Plannotator Code Review

skills CLI
$ npx skills add backnotprop/plannotator --skill plannotator-review -a claude-code

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

GitHub CLI
$ gh skill install backnotprop/plannotator plannotator-review --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/backnotprop/plannotator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/apps/skills/core/plannotator-review .claude/skills/plannotator-review && 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
plannotator-review
GitHub stars
9.2k
Token cost
~332 tokens
SKILL.md length
154 words
Files
2
Skills in repo
13
Repo updated
First seen
Licence
Apache-2.0

At a glance

Opens Plannotator's browser-based review UI for the current worktree, another directory or a pull request URL, then applies the feedback it returns.

  • Works in 4 steps: Launch the command with Bash. → Wait for it to finish. → If it returns feedback or annotations,… → …
  • Reviewing local changes in a visual interface instead of reading a diff in chat
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Reviewing one layer of a stacked branch against the branch below it

What it does

This skill runs the plannotator review command with Bash instead of showing a diff inline. The command takes an optional --base reference, a --diff-type option and a directory or pull request URL, and it opens a review interface in the browser for the chosen changes.

The agent waits for the command to finish. If feedback or annotations come back, it addresses them in the same conversation, applying changes in the directory the feedback names, and an approval message is acknowledged before work continues. For a stacked branch, passing --base with the branch directly below yours limits the review to what that layer adds. Both flags last for one session only and work with git repositories alone. Paths with spaces need quoting, and the agent runs the command itself rather than asking you to paste it.

When your agent uses it

  • Reviewing local changes in a visual interface instead of reading a diff in chat
  • Reviewing one layer of a stacked branch against the branch below it
  • Reviewing a pull request by URL and acting on the comments

Example prompts

  • “Open Plannotator to review my current changes.”
  • “Run a plannotator review on ../feature-worktree and fix whatever the feedback asks for.”
  • “Review this stacked branch layer in Plannotator, using the branch below it as the base.”
  • “Review the pull request at https://github.com/acme/webapp/pull/7 in Plannotator.”

Requirements

  • The `plannotator` CLI
  • A git repository, since the base and diff-type flags are git-only

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Launch the command with Bash.
  2. Wait for it to finish.
  3. If it returns feedback or annotations, address them in the same conversation.
  4. If it returns an approval/LGTM-style message, acknowledge that review passed and continue.

What it can do on your machine

Read from SKILL.md and the folder at commit 1d9fe3f. 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 (its code samples are bash).

    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

Plannotator Code Review loads about 332 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 154 words of instructions outside code blocks.

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

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 backnotprop/plannotator at commit 1d9fe3f, republished under its Apache-2.0 licence (© backnotprop). 154 words, ~332 tokens.

Download SKILL.mdSave it as .claude/skills/plannotator-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
plannotator-review
description
Open Plannotator's browser-based code review UI for the current worktree, another directory, or a pull request URL, then act on the feedback that comes back.
disable-model-invocation
true

Plannotator Review

Use this skill when the user wants to review current code changes in Plannotator instead of reading a diff inline.

Run:

bash
plannotator review [--base <ref>] [--diff-type <type>] [directory-or-pr-url]

Reviewing one layer of a stacked branch? Pass --base <the branch immediately below yours> so the review shows only what this layer adds, instead of everything since main. Both flags are session-only (the reviewer can change either in the UI; nothing is persisted) and git-only.

To review another repository or worktree, pass its directory (relative to the current session or absolute), e.g. plannotator review ../feature-worktree. Quote paths containing spaces. Feedback names the selected directory; apply changes there.

Behavior:

  1. Launch the command with Bash.
  2. Wait for it to finish.
  3. If it returns feedback or annotations, address them in the same conversation.
  4. If it returns an approval/LGTM-style message, acknowledge that review passed and continue.

Do not ask the user to copy shell commands into chat. Run the command yourself.

© backnotprop, Apache-2.0. 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 1 other file in apps/skills/core/plannotator-review of backnotprop/plannotator.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 1d9fe3f

Compare with similar skills

Plannotator Code 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.

Plannotator Code Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Plannotator Code Review this skillbacknotprop/plannotator9.2k—~332Automated safety check: PassApache-2.0
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything85k1 repos~1.4kAutomated safety check: PassMIT
Open Code Review CLIalibaba/open-code-review44k—~3.1kAutomated safety check: PassApache-2.0
PR Review State Fetchprisma/orm48k—~767Automated safety check: PassApache-2.0
Knowledge Graph PR Reviewtirth8205/code-review-graph32k—~452Automated safety check: PassMIT

Similar skills

  • 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.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    85k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • Open Code Review CLI

    alibaba/open-code-review

    Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.

    44k GitHub stars~3.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Official

    Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.

    48k GitHub stars~767 tokensUpdated today
    DevelopmentAuto-check passed
  • Knowledge Graph PR Review

    tirth8205/code-review-graph

    Reviews a pull request or branch diff with a code knowledge graph and produces a structured review that includes blast-radius analysis.

    32k GitHub stars~452 tokensUpdated today
    DevelopmentAuto-check passed
  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

More from backnotprop/plannotator

All 13 skills in this repo
  • Plannotator Visual Explainer

    backnotprop/plannotator

    Builds self-contained HTML explainers for plans, pull requests and technical concepts in Plannotator's theme, then opens them in its annotation view.

    9.2k GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed
  • Plannotator Release Preparation

    backnotprop/plannotator

    Drafts Plannotator release notes with full contributor credit, bumps versions in dependency order, builds, and starts the tag-driven release pipeline, in four reviewed phases.

    9.2k GitHub stars~4.6k tokensUpdated yesterday
    Auto-check passed
  • Plannotator Planning Analysis

    backnotprop/plannotator

    Mines a Plannotator archive of denied plans for feedback patterns and prompt improvements, then writes an HTML dashboard report, with a Claude Code fallback.

    9.2k GitHub stars~6.7k tokensUpdated yesterday
    Auto-check passed
  • Renovate Actions PR Review

    backnotprop/plannotator

    Reviews Renovate pull requests that bump GitHub Actions by checking pinned SHAs against upstream tags, scanning changelogs and confirming workflows stay compatible.

    9.2k GitHub stars~640 tokensUpdated yesterday
    Auto-check passed
  • Plannotator Goal Setup

    backnotprop/plannotator

    Guides the agent from a vague objective to a written goal package under goals/, using a confirmed restatement, a browser interview, a fact sheet and a codebase pass.

    9.2k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Dependency Update Audit

    backnotprop/plannotator

    Audits outdated npm and Bun packages for supply chain integrity before bumping them, deferring risky ones and logging every decision.

    9.2k GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Plannotator Code Review

What does Plannotator Code Review do?

Opens Plannotator's browser-based review UI for the current worktree, another directory or a pull request URL, then applies the feedback it returns. This skill runs the plannotator review command with Bash instead of showing a diff inline. The command takes an optional --base reference, a --diff-type option and a directory or pull request URL, and it opens a review interface in the browser for the chosen changes.

When should I use Plannotator Code Review?

Plannotator Code Review fits situations like: reviewing local changes in a visual interface instead of reading a diff in chat; reviewing one layer of a stacked branch against the branch below it; reviewing a pull request by URL and acting on the comments.

How do I install Plannotator Code Review in Claude Code?

Run `npx skills add backnotprop/plannotator --skill plannotator-review -a claude-code`. Or copy the skill folder (apps/skills/core/plannotator-review in backnotprop/plannotator) into .claude/skills/plannotator-review in your project. Claude Code loads it when a task matches its description.

How do I install Plannotator Code Review in Codex?

Run `npx skills add backnotprop/plannotator --skill plannotator-review -a codex`. Or copy the skill folder (apps/skills/core/plannotator-review in backnotprop/plannotator) into .agents/skills/plannotator-review in your project. Codex loads it when a task matches its description.

Can I use Plannotator Code 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 backnotprop/plannotator --skill plannotator-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/plannotator-review, .gemini/skills/plannotator-review, .github/skills/plannotator-review and .opencode/skills/plannotator-review in your project.

What does Plannotator Code Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Plannotator Code Review is instructions for the agent only. Our summary lists: The `plannotator` CLI; A git repository, since the base and diff-type flags are git-only.

Does Plannotator Code 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 Plannotator Code 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 Plannotator Code Review use?

Plannotator Code Review is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Plannotator Code Review use?

About 332 tokens (SKILL.md is roughly 1.3k 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 Plannotator Code Review?

Skills that share tags, products or a category with Plannotator Code Review: Finishing a Development Branch (obra/superpowers, 296k stars), Understand Diff Analysis (Egonex-AI/Understand-Anything, 85k stars), Open Code Review CLI (alibaba/open-code-review, 44k stars) and PR Review State Fetch (prisma/orm, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Plannotator Code Review?

backnotprop (a GitHub user) maintains it in backnotprop/plannotator, which has 9,185 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 6, 2026.

Source: backnotprop/plannotator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.