plannotator-annotate
Open Plannotator's annotation UI for a markdown file, HTML file, URL, or folder and then respond to the returned annotations.
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.
Claude Code
$ npx -y skills add backnotprop/plannotator --skill plannotator-review --agent claude-code
Codex
$ npx skills add backnotprop/plannotator --skill plannotator-review -a codex -y
Cursor
$ npx skills add backnotprop/plannotator --skill plannotator-review -a cursor -y
Gemini CLI
$ npx skills add backnotprop/plannotator --skill plannotator-review -a gemini-cli -y
GitHub Copilot
$ npx skills add backnotprop/plannotator --skill plannotator-review -a github-copilot -y
OpenCode
$ npx skills add backnotprop/plannotator --skill plannotator-review -a opencode -y
Windsurf
$ npx skills add backnotprop/plannotator --skill plannotator-review -a windsurf -y
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. allowed-tools: Bash(plannotator:*) disable-model-invocation: true
Arguments pass through to `plannotator review`: one directory or PR/MR URL, `--git` / `--gitbutler`, and the session-only open-state flags `--base <ref>` / `--diff-type <type>` (git-only; for a stacked branch, `--base <the branch below yours>` reviews just that layer).
For another repository or worktree, pass its path relative to this session or an absolute path, e.g. `/plannotator-review ../feature-worktree`. Quote paths containing spaces. Supply a target, not prose; feedback names the directory where changes belong.
!`plannotator review $ARGUMENTS`
If the review above contains feedback or annotations, address them in the same conversation. If no changes were requested (an approval/LGTM-style result), acknowledge that review passed and continue.
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.
If the review was moved to the background, wait for it to finish. If Claude Code stopped it at its background time limit before the user decided, tell the user, and only when they ask, run `plannotator review $ARGUMENTS` again with `run_in_background` and `timeout: 7200000`: their annotations are restored from the saved draft.
Plannotator is a local, browser-based review surface for AI coding agents: Claude Code, Codex, Copilot CLI, Gemini CLI, OpenCode, Kiro, Droid, Amp, DeepSeek Harness, and Pi. It plugs directly into your agent through its hooks and commands.
Open Plannotator's annotation UI for a markdown file, HTML file, URL, or folder and then respond to the returned annotations.
Open Plannotator on the latest rendered assistant message and use the returned annotations to revise that message or continue.
Open the Plannotator Inbox in the browser (starting it if needed), say its address, and learn how to use the Inbox for the rest…
Reference for using Plannotator (its `plannotator` tool when you have one, otherwise the CLI): plan review, code review,…
Analyze a user's Plannotator plan archive to extract denial patterns, feedback taxonomy, evolution over time, and actionable…
Turn an idea or objective into a goal package for /goal. Interviews the user, builds a reviewed fact sheet via Plannotator, then…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.