Review code changes in Plannotator’s browser interface for the current worktree, another directory, or a pull request URL. Use the returned annotations or approval to guide the next step, including addressing requested changes in the selected worktree.
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.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
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]
Run it with the shell tool's is_background: true, and no trailing &. The command waits until the person finishes the review in the browser, which often takes longer than the shell tool's foreground limit (2 minutes by default, 10 at most); a foreground run would be stopped and the review lost. Then end your turn without stopping the task. When the task finishes, read its output (the tool result names the output file) and act on it.
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:
Do not ask the user to copy shell commands into chat. Run the command yourself.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use Plannotator to review plans, code changes, documents, and running local apps in a browser. This reference covers returning feedback to agents, browsing past decisions, sharing guided code reviews, and leaving questions for later replies.
Collect comments on a Markdown or HTML document, plain-text configuration file, URL, or folder through Plannotator’s annotation interface. Use the returned notes to revise the material; with gated review, a plan or specification can also receive an approval decision.
Review Markdown files, HTML files, URLs, or folders in Plannotator’s annotation interface. The agent responds to requested changes and distinguishes them from approvals, optional approval notes, and sessions closed without feedback.
Open files, folders, or URLs in Plannotator’s annotation interface, then have the agent address the returned comments. Use it to review Markdown, plain-text configuration files, or HTML through a shared feedback workflow.
Analyze rejected plans and reviewer feedback to identify recurring concerns, changing expectations, and concrete prompt improvements. Produce an HTML dashboard from Plannotator archives, or use Claude Code plan rejection reasons when those archives are unavailable.
Open the Plannotator Inbox in a browser, starting it in the background if needed, and give the user its address. Useful when they have closed the tab or need to find the Inbox again.