plannotator

Review plans, code diffs, and documents through a browser-based annotation CLI.

9|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/Yassimba/loom --skill plannotator-yassimba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plannotator
Source: https://github.com/Yassimba/loom/tree/main/skills/plannotator
Command: npx skills add https://github.com/Yassimba/loom --skill plannotator-yassimba

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires plannotator.

What problem does it solve? Getting structured human feedback on agent-generated plans, code changes, and documents is slow and unstructured. Plannotator opens plans, diffs, and files in a local browser annotation UI and returns the reviewer's decisions and annotations to the agent on stdout. ## Core Features & Use Cases - Plan and Code Review: Review local VCS changes (Git, GitButler, JJ, P4) or GitHub/GitLab pull requests with plannotator review, with feedback returned as plaintext or JSON. - Document and URL Annotation: Annotate markdown, config files, HTML pages, web URLs, running local apps, or folders with plannotator annotate. - Approval Gates and Guided Reviews: Enforce machine-checkable approval gates with exit codes, browse archived plan decisions, and export or share encrypted Guided Review walkthroughs. - Use Case: After an agent produces a plan, the plan-review hook opens it in the browser; the human annotates concerns, and the structured feedback returns to the agent to address in the same conversation. ## Quick Start Use the plannotator skill to review my current uncommitted code changes and return the reviewer's feedback.

Frequently Asked Questions about plannotator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a GitHub pull request with plannotator?

Run plannotator review followed by the PR URL, such as plannotator review https://github.com/owner/repo/pull/123. It requires an authenticated gh or glab CLI and builds a local checkout of the PR head by default for full file access.

How do I annotate a markdown file or web page from the CLI?

Run plannotator annotate followed by the file path or https URL. Markdown, text, config, and HTML files open directly, while URLs are fetched and converted via Jina Reader unless you pass --no-jina.

Does plannotator work over SSH or in devcontainers?

Yes, set PLANNOTATOR_REMOTE=1 to force remote mode, which uses fixed port 19432 with a wide bind. You can also publish a session over your tailnet with the --tailscale flag for HTTPS access.

Why does plannotator annotate refuse .env and source-code files?

The annotate command deliberately refuses .env files because they commonly hold secrets and annotate history copies file contents. Source-code files belong to plannotator review, which handles code diffs instead.

How do I get machine-readable output from a plannotator review?

Add the --json flag to receive one JSON record with decision and feedback fields. For a strict approval gate, combine --gate --json with --require-approval so the exit code reports the human outcome.