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.

1,039
installs: 0 up / 0 down, score 0.00
votes: 9,863
repo stars
Updated: less than a month ago
In the catalog since: 7 Nov 2026
From: backnotprop/plannotator

Get it through your agent npx skills add backnotprop/plannotator@plannotator-review

Skill instructions

Rendered from the published SKILL.md, 18 lines.

Plannotator Review

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.

Code review feedback

!plannotator review $ARGUMENTS

Your task

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.

Get it through your agent

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "plannotator-review"
  }
}

New to this? Set up Graph-of-Skills or get a free key. The text on this page comes from its authors: how skills are sourced and what we check. If none fits your task, your agent can write a skill for your own library. To keep a skill from your own library on a machine, see how to install one of your skills.

Share on X Share on LinkedIn Share on Bluesky Share on Hacker News

Share on Reddit

Source

Source repository backnotprop/plannotator
Listing on skills.sh

From backnotprop/plannotator via skills.sh

Related skills

difit-review
Review a specific diff (branch, commit, or GitHub PR) and show the findings as comments inside difit, the local diff viewer. Explicit opt-in only — use when the user explicitly names difit, asks to open or annotate the review in the difit viewer, or invokes this skill by name. For ordinary requests to review code, diffs, commits, branches, or pull requests, review normally and respond in the conversation without launching difit.
1,939 installs
review-pr
Review an existing GitHub pull request and post inline review comments on its diff. Use when the changes are on an opened PR rather than your local working tree.
1,256 installs
review-request
You MUST use this when a completed or partially committed implementation needs an independent code review against explicit requirements, a defined task scope, and the actual Git diff, including committed and working-tree changes.
2,125 installs
open-code-review
Performs AI-powered code review on Git changes using the `ocr` CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply fixes when requested. With appropriate review rules, can detect various types of issues including bugs, security vulnerabilities, performance problems, and code quality concerns.
7,274 installs
review-local-changes
Review your local uncommitted working-tree changes (git diff plus untracked files) and return actionable improvement suggestions. Use before committing, when nothing has been pushed yet.
1,309 installs

More from backnotprop/plannotator

plannotator-visual-explainer
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.
13,878 installs
plannotator-compound
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.
12,762 installs
plannotator-setup-goal
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.
12,525 installs
plannotator-annotate
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.
1,030 installs
plannotator-last
Open Plannotator on the latest rendered assistant message and use the returned annotations to revise that message or continue.
1,006 installs

Content is provided as published by its creators; you are responsible for how you use it.

To request removal, use the contact form.