vscode-diff-review

Generate structured diff-review markdown files for VSCode/Cursor workflows.

4|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/rbaumier/skills --skill vscode-diff-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vscode-diff-review
Source: https://github.com/rbaumier/skills/tree/main/vscode-diff-review
Command: npx skills add https://github.com/rbaumier/skills --skill vscode-diff-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The Diff Review tool helps you generate structured markdown review files to organize code reviews for the vscode-diff-review workflow.

Core Features & Use Cases

  • Generate a review .md file in reviews/ (relative to the git repo root) for the vscode-diff-review extension.
  • Support both commit-vs-commit and working-tree diff modes, capturing status for each changed file.
  • The extension renders the review diffs in Cursor/VSCode, enabling streamlined review cycles.

Quick Start

Run the bundled script from the git repository root to generate a new diff review file and display its path.

Frequently Asked Questions about vscode-diff-review

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

FAQPage Schema
How do I generate a markdown diff review file for a VSCode git workflow?

To generate a markdown diff review for VSCode, run the bundled create-review.sh script from your git repository root. It outputs a structured markdown file with frontmatter and a list of modified items under the reviews/ directory.

What is a structured diff review file and when do I need one?

A structured diff review file is a markdown document capturing commit-to-commit or working-tree changes with frontmatter metadata. You need one to document and organize code reviews for rendering inside VSCode or Cursor workflows.

Does this diff review tool require a specific git repository context?

Yes, generating diff review files requires an active git repository context and the scripts/create-review.sh tool. The script parses your working-tree or commit-to-commit diffs to capture the status of each changed file.

Can I review working-tree diffs versus commit-to-commit changes in VSCode?

Yes, you can review both working-tree and commit-to-commit diffs. The generated markdown file includes frontmatter specifying the mode, left/right commit labels, and a files list of modified items for the extension to render.

What is the best way to document code changes for a Cursor review cycle?

The best way to document code changes for Cursor is generating a date-slug markdown review file. This file structures your modified items list and diff mode, enabling the extension to render streamlined review cycles directly in the editor.