Open Plannotator's browser-based code review UI and address the returned feedback.
64
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Run:
PLANNOTATOR_ORIGIN=kiro-cli plannotator reviewYou may append one directory or PR URL:
PLANNOTATOR_ORIGIN=kiro-cli plannotator review <pr-url>
PLANNOTATOR_ORIGIN=kiro-cli plannotator review ../feature-worktreeDirectory 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>]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.
backnotprop/plannotator
bbcaa97
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.