npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

plan-review

v1.1.5

Published

Interactive CLI for reviewing AI-generated markdown plans

Readme

plan-review

Interactive CLI for reviewing AI-generated markdown plans. Parses a plan into sections, opens a three-panel browser review UI, collects line-anchored comments, and pipes structured feedback back — to the AI that wrote the plan, your clipboard, or a file.

Browser mode demo

Install

npm install -g plan-review

Claude Code skill (optional)

If you use Claude Code, install the companion skill so you can say "review this plan":

plan-review install-skill

Quick start

# Review a plan — opens the browser UI (default)
plan-review path/to/plan.md

# Try the included fixture
plan-review examples/renderer-fixture.md

# Pipe feedback directly back to Claude
plan-review path/to/plan.md -o claude

That's it. The browser mode is the default and the recommended way to review plans — line-anchored comments, auto-save, full markdown rendering including mermaid, math, footnotes, and admonitions.

Browser mode (default)

Three panels:

+------------------+----------------------------+------------------+
|                  |                            |                  |
|   Table of       |   Rendered markdown        |   Comment        |
|   Contents       |   with plan metadata       |   Sidebar        |
|                  |                            |                  |
|   - Milestone 1  |   ## Task 1.1              |   [Add comment]  |
|     * Task 1.1 ✓ |                            |                  |
|     * Task 1.2   |   **Depends on:** 1.0      |   > "Line 3-5"   |
|   - Milestone 2  |   **Blocks:** 1.2          |   Fix the error  |
|     * Task 2.1   |                            |   handling here  |
|                  |   Content with line        |                  |
|                  |   gutters for anchoring    |   [Submit Review]|
|                  |   comments to ranges       |                  |
+------------------+----------------------------+------------------+

Line-anchored comments. Click a gutter marker to start a selection, shift-click another line to extend the range. Comments anchor to the exact lines and travel back in the output.

Section-level comments. "Add comment to entire section" under any section header when line-level granularity isn't needed.

Auto-save. Your progress writes to ~/.plan-review/sessions/ as you work. Close the tab, come back later, pick up where you left off. Closing the tab mid-review exits the CLI cleanly with the session preserved.

Full markdown rendering. Paragraphs, nested lists, task lists, tables, code fences, blockquotes, GFM admonitions (> [!NOTE]), footnotes, inline HTML (<kbd>, <sub>, <sup>, <details>), emoji shortcodes, horizontal rules, images, reference-style links — plus mermaid diagrams and KaTeX math, both lazy-loaded from CDN only when the plan contains them.

Terminal mode (--cli)

For SSH sessions, CI, or headless environments where launching a browser isn't an option:

plan-review path/to/plan.md --cli

Interactive terminal UI with a table of contents, section navigation, and inline commenting.

| Command | Action | |---------|--------| | all | Linear review through all sections | | 1.1 | Jump to a specific section | | done / q | Finish review | | toc | Return to table of contents | | back | Go to previous section | | (enter) | Skip section | | (any text) | Add comment on current section |

Terminal mode is a fallback — you get text rendering and section-level comments, but no line anchors, no mermaid, no math, no live markdown preview.

Options

-o, --output <target>   Output target: stdout, clipboard, file, claude
--output-file <path>    Custom output file path (with --output file)
--split-by <strategy>   Force split strategy: heading, separator
--fresh                 Skip session resume, start clean review
--cli                   Use the terminal review UI instead (SSH/CI/headless)
-V, --version           Show version
-h, --help              Show help

The AI feedback loop

The point is closing the loop between AI-generated plans and human review:

AI writes plan  →  You review with plan-review  →  Feedback pipes to Claude  →  AI revises
# Review in browser, send structured feedback straight to Claude
plan-review plan.md -o claude

Line-anchored, section-scoped comments become input the AI can act on — not a wall of prose in a chat message.

How it works

  1. Parses your markdown — auto-detects plan-style documents (milestones, tasks, dependencies) or falls back to generic heading-based splitting.
  2. Renders in the browser by default, or in the terminal via --cli.
  3. Collects your comments as you review each section.
  4. Outputs structured markdown with your comments alongside the original content.

Plan mode

Documents with ## Milestone / ### Task hierarchy and fields like **Depends On:**, **Blocks:**, **Verification:** are detected as plans. Sections show dependency metadata and task IDs in the sidebar.

Generic mode

Any markdown with headings gets split into reviewable sections. Non-plan docs still work — you just don't get the plan-specific chrome.

Output targets

  • stdout — print to terminal (default when not prompted otherwise)
  • clipboard — copy to clipboard (pbcopy/xclip)
  • file — write to <input>.review.md or a custom path via --output-file
  • claude — pipe directly to the Claude Code CLI

Saved sessions

Review progress auto-saves as you work. Re-running plan-review on the same file prompts to resume. Stored in ~/.plan-review/sessions/.

plan-review plan.md --fresh    Skip session resume, start clean
plan-review sessions           List all saved sessions

Manual cleanup: delete files in ~/.plan-review/sessions/.

VS Code extension

Review plans inside VS Code without leaving the editor. See packages/vscode-extension/README.md for install and usage.

License

MIT