plannotator-review
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.
- Installs
- 776
- Last 24h
- +23
- Trending rank
- #5247
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/backnotprop/plannotator --skill plannotator-review- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads plannotator-review automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Plannotator Review
Use this skill when the user wants to review current code changes in Plannotator instead of reading a diff inline.
Run:
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:
- Launch the command with Bash.
- Wait for it to finish.
- If it returns feedback or annotations, address them in the same conversation.
- If it returns an approval/LGTM-style message, 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.
Do not ask the user to copy shell commands into chat. Run the command yourself.
FAQ
What does the plannotator-review skill do?
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.
How do I install plannotator-review?
Run npx skills add https://github.com/backnotprop/plannotator --skill plannotator-review in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/plannotator-review/ (personal) or .claude/skills/plannotator-review/ (project).
Which AI agents can use plannotator-review?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is plannotator-review safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains plannotator-review?
It is published by backnotprop in backnotprop/plannotator. It has 776 recorded installs.
More from backnotprop/plannotator
plannotator-visual-explainer
backnotprop/plannotator
Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.
plannotator-compound
backnotprop/plannotator
Analyze a user's Plannotator plan archive to extract denial patterns, feedback taxonomy, evolution over time, and actionable prompt improvements — then produce a polished HTML dashboard report. Falls back to Claude Code ExitPlanMode denial reasons when Plannotator data is unavailable.
plannotator-setup-goal
backnotprop/plannotator
Turn an idea or objective into a goal package for /goal. Interviews the user, builds a reviewed fact sheet via Plannotator, then explores the codebase to produce an execution plan.
plannotator-annotate
backnotprop/plannotator
Open Plannotator's annotation UI for a markdown file, plain-text config file (.yaml, .json, .toml, .ini, .csv, .log, …), HTML file, URL, or folder and then respond to the returned annotations.
plannotator-last
backnotprop/plannotator
Open Plannotator on the latest rendered assistant message and use the returned annotations to revise that message or continue.
release-plannotator
backnotprop/plannotator
Prepare and execute a Plannotator release — draft release notes with full contributor credit, bump versions across all package files, build in dependency order, and kick off the tag-driven release pipeline. Use this skill whenever the user mentions preparing a release, bumping versions, writing release notes, tagging a release, or publishing. Also trigger when the user says things like "let's ship", "prep a release", "what's changed since last release", or "time to cut a new version".
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.