Files
leo-claude-mktplace/plugins/pr-review/commands/pr-diff.md
lmiranda 2d51df7a42 feat(marketplace): command consolidation + 8 new plugins (v8.1.0 → v9.0.0) [BREAKING]
Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action>
sub-command pattern. Git-flow consolidated from 8→5 commands (commit
variants absorbed into --push/--merge/--sync flags). Dispatch files,
name: frontmatter, and cross-reference updates for all plugins.

Phase 2: Design documents for 8 new plugins in docs/designs/.

Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate,
saas-react-platform, saas-test-pilot, data-seed, ops-release-manager,
ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents,
skills, README, and claude-md-integration. Marketplace grows from 12→20.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-06 14:52:11 -05:00

1.1 KiB

name, description, agent
name description agent
pr diff Formatted diff with inline review comments coordinator

/pr diff - Annotated PR Diff Viewer

Visual Output

Display header: PR-REVIEW - Diff Viewer

Skills to Load

  • skills/mcp-tools-reference.md
  • skills/pr-analysis.md
  • skills/output-formats.md

Usage

/pr diff <pr-number> [--repo owner/repo] [--context <n>] [--no-comments] [--file <pattern>]

Workflow

Step 1: Fetch Data

Load MCP tools, then: get_pr_diff, get_pr_comments

Step 2: Parse and Annotate

Execute skills/pr-analysis.md Annotated Diff Display:

  • Overlay comments at file/line positions
  • Show commenter, timestamp, replies
  • Mark resolved vs open

Step 3: Display

Use annotated diff format from skills/output-formats.md

Use Cases

  • Review preparation with existing feedback
  • Followup work - see what was commented
  • Progress tracking on resolved comments
Command Purpose
/pr summary Quick overview
/pr review Full review
/pr findings Filter findings