dev-review

Author JSON code reviews for branches, commits, and pull requests via the Review Desktop server.

137|10|Updated Aug 18, 2026
One-click install
npx skills add https://github.com/devdotfast/review --skill dev-review-devdotfast
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-review
Source: https://github.com/devdotfast/review/tree/main/packages/review/skills/dev-review
Command: npx skills add https://github.com/devdotfast/review --skill dev-review-devdotfast

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing agent-written code as raw diffs makes it hard to understand architecture, data flow, and intent behind large changes. This Skill lets an agent author structured, guided JSON reviews of a branch, jj change, or pull request through the running Review Desktop server, and answer product questions about Review itself. ## Core Features & Use Cases - JSON Review Authoring: Register a repository, create or reuse a review targeting a worktree or pinned commits, build an outline of sections, and fill each with verified source evidence, diagrams, and trace excerpts using review MCP tools or the review api CLI. - Rich Review Components: Insert sequence diagrams, code peeks, source links, software maps, and uploaded images or trace resources, with server-side validation of every edit. - Product Q&A: Answer questions about Review Desktop capabilities, setup, CLI, privacy, telemetry, and troubleshooting from the bundled documentation. - Use Case: After an agent implements a feature on a branch, ask it to review the branch against main; the Skill creates a review with a summary, design decisions, and cited source evidence that opens directly in the Review Desktop app. ## Quick Start Ask your agent to review the current branch against main and open the result in Review Desktop.

Frequently Asked Questions about dev-review

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

FAQPage Schema
How do I create a code review for a branch or pull request?

Register the local checkout with review_register_repository, then call review_create with a target of kind worktree or commits. For a PR, include its canonical GitHub URL so the review retains its identity, then open it with review_open.

How do I review changes introduced by a single commit?

Use a target of kind commits with the commit as head and its parent as base. Omitting the base shows source at head with no diff, so supplying the parent is required to review one commit's changes.

Does Review Desktop need to be running to author a review?

Yes. The desktop server owns all JSON content, saved versions, and source pins. The Skill communicates through review MCP tools or the review api CLI, and the app must be started explicitly before authoring or opening a review.

Can I add diagrams or images to a review?

Yes. Upload images, trace excerpts, or software maps with review_upload, then insert components like sequence diagrams or software_map nodes referencing the returned resource ID. The server validates all components before saving.

What is the difference between worktree and commits review targets?

A worktree target follows the checkout's current saved files, including working changes against HEAD. A commits target pins immutable base and head revisions, using separate prepared checkouts for language-server navigation.

Why is language-server navigation not working in a pinned review?

Pinned checkouts lack your working copy's dependencies. Configure setup commands with git config devfast.prepare, then call review_environment with retry:true to rerun preparation if acquisition failed.