Open Plannotator’s browser-based code review interface from Kiro and address the returned feedback. Review the current directory, another working directory, or a pull request URL, and optionally choose a comparison base to focus the changes shown.
Open Plannotator's browser-based code review UI and address the returned feedback.
Review the instructions the agent will receive before you install.
Run:
PLANNOTATOR_ORIGIN=kiro-cli plannotator review
You may append one directory or PR URL:
PLANNOTATOR_ORIGIN=kiro-cli plannotator review <pr-url>
PLANNOTATOR_ORIGIN=kiro-cli plannotator review ../feature-worktree
Directory paths are relative to the current session or absolute. Quote paths containing spaces. Feedback names the directory where changes belong.
Or open the session against a specific base / diff mode (session-only, git-only; for a stacked branch, --base <the branch below yours> reviews just that layer):
PLANNOTATOR_ORIGIN=kiro-cli plannotator review --base <ref> [--diff-type <type>]
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 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.
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.
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.