Skip to main content
skill CX Codex

plannotator-review — Claude Code skill: what it does, how to install

Launches Plannotator's browser UI for code review and feeds feedback back to the agent. Helpful for inspecting diffs and stacked branches.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add backnotprop/plannotator --skill plannotator-review -a claude-code
Open on GitHub

What plannotator-review does

The skill launches the Plannotator code review UI by running PLANNOTATOR_ORIGIN=kiro-cli plannotator review. You can supply a PR address, a target directory, or filter changes using --base <ref> and --diff-type <type>. The diff inspection supports both session-only and git-only modes.

Model invocation is disabled via disable-model-invocation: true. When a review session closes with no comments, the agent reports this in one line and stops right away. An empty closure never counts as approval.

What it helps with

  • inspect pull request diffs inside a browser interface
  • isolate and review a single layer of a stacked branch with --base
  • pass browser-based review feedback directly to the agent
  • halt execution automatically when a review closes without feedback

Example prompts for the agent

  • Open Plannotator review for the current session
  • Review changes against base branch main
  • Run Plannotator review on ../feature-worktree

How to install plannotator-review

1Skills CLI (Vercel)

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

2Manually: put the files in place

~/.claude/skills/plannotator-review/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/plannotator-review/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about plannotator-review

How to install plannotator-review in Claude Code?

Run npx skills add backnotprop/plannotator --skill plannotator-review -a claude-code in your terminal.

What does plannotator-review do?

It opens a local web UI to inspect code diffs and returns your review notes directly to the coding assistant.

What happens if the review UI is closed without comments?

The assistant acknowledges the empty session and halts. Closing the interface without comments is not an approval to edit code.

Source text

SKILL.md · Apache-2.0
---
name: plannotator-review
disable-model-invocation: true
description: Open Plannotator's browser-based code review UI and address the returned feedback.
---

# Plannotator Review (Kiro)

Run:

```bash
PLANNOTATOR_ORIGIN=kiro-cli plannotator review
```

You may append one directory or PR URL:

```bash
PLANNOTATOR_ORIGIN=kiro-cli plannotator review <pr-url>
PLANNOTATOR_ORIGIN=kiro-cli plannotator review ../feature-worktree
```

Directory paths are relative to the current session or absolute. Quote paths containing spaces. Feedback names the directory where changes belong.

Or open the session against a specific base / diff mode (session-only, git-only; for a stacked branch, `--base <the branch below yours>` reviews just that layer):

```bash
PLANNOTATOR_ORIGIN=kiro-cli plannotator review --base <ref> [--diff-type <type>]
```

If the session closes without feedback (the output is "Review session closed without feedback." or empty), acknowledge it in one sentence and stop. Do not begin any work: closing the session is not approval.

© backnotprop · Apache-2.0 · backnotprop/plannotator

Similar skills

Everything for Code review and refactoring →

From the same set5

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor