Review code changes in Plannotator’s browser interface and have the agent address returned comments. Choose the current working directory, another checkout, or a pull or merge request URL, with options to focus on a specific comparison base.
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.
Review the instructions the agent will receive before you install.
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 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.
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.
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.
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 documents, text configuration files, HTML, URLs, or folders in Plannotator for browser review. The agent responds to returned annotations and can use an approval session when you need to accept a plan, specification, or document.
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 assistant’s latest rendered message in Plannotator and return specific annotations for revision. The skill distinguishes requested edits from approval, approval with notes, and a closed session, so each review result receives the appropriate response.