lmiranda
2d51df7a42
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>
48 lines
814 B
Markdown
48 lines
814 B
Markdown
---
|
|
name: pr summary
|
|
description: Quick summary of PR changes
|
|
agent: coordinator
|
|
---
|
|
|
|
# /pr summary - Quick PR Summary
|
|
|
|
## Visual Output
|
|
|
|
Display header: `PR-REVIEW - Quick Summary`
|
|
|
|
## Skills to Load
|
|
|
|
- skills/mcp-tools-reference.md
|
|
- skills/pr-analysis.md
|
|
- skills/output-formats.md
|
|
|
|
## Usage
|
|
|
|
```
|
|
/pr summary <pr-number> [--repo owner/repo]
|
|
```
|
|
|
|
## Workflow
|
|
|
|
### Step 1: Fetch PR Data
|
|
|
|
Load MCP tools, then: `get_pull_request`, `get_pr_diff`
|
|
|
|
### Step 2: Analyze Changes
|
|
|
|
Execute `skills/pr-analysis.md`:
|
|
- Categorize changes (feature, fix, refactor)
|
|
- Calculate statistics
|
|
- Identify key files
|
|
- Assess scope and risk
|
|
|
|
### Step 3: Generate Summary
|
|
|
|
Use summary format from `skills/output-formats.md`
|
|
|
|
## When to Use
|
|
|
|
- Quick overview before full review
|
|
- Triage multiple PRs
|
|
- Decide if `/pr review` is needed
|