devflow-review-pr
npx machina-cli add skill docutray/docutray-claude-code-plugins/devflow-review-pr --openclawDevFlow: Pull Request Review Flow
Perform complete technical review of Pull Requests, including branch checkout, technical validation, error correction, and quality approval.
When to Use
Use this flow when you need to:
- Review a pull request technically
- Validate PR quality before merge
- Check out and test PR changes
- Approve or request changes on PR
Flow Diagram
flowchart TD
A([BEGIN]) --> B[Fetch PR info from GitHub]
B --> C[Identify linked issue]
C --> D[Analyze modified files]
D --> E[Checkout PR branch]
E --> F[Install dependencies if needed]
F --> G[Run technical validations]
G --> H{Validation passed?}
H -->|No| I{Auto-fix enabled?}
I -->|Yes| J[Auto-correct issues]
J --> G
I -->|No| K[Report issues to user]
K --> L[User decides action]
H -->|Yes| L
L --> M{Functional tests configured?}
M -->|Yes| N[Start local server]
N --> O[Run functional tests]
O --> P[Capture evidence]
M -->|No| Q[Skip functional tests]
P --> R[Consolidate results]
Q --> R
R --> S[Classify findings by severity]
S --> T{Auto-approve & no critical issues?}
T -->|Yes| U[Auto-approve PR]
T -->|No| V[Present review to user]
V --> W{User decision?}
W -->|Approve| X[Approve PR]
W -->|Comment| Y[Add review comments]
W -->|Request changes| Z[List required changes]
U --> AA([END])
X --> AA
Y --> AA
Z --> AA
Node Details
1. PR Analysis
- Fetch PR details from GitHub
- Identify linked issue for context
- Analyze changed files and impact
2. Environment Setup
- Checkout PR branch (handle forks)
- Install/update dependencies
- Ensure clean test environment
3. Technical Validation
Run complete validation suite:
- Tests
- Linting
- Type checking
- Build
4. Auto-Fix (Optional)
If --fix-issues flag and validation fails:
- Attempt automatic corrections
- Re-run validations
- Report what was fixed
5. Functional Testing (Optional)
If configured in .claude/details/commands/review-pr.md:
- Start local server
- Run automated functional tests
- Capture screenshots/logs as evidence
6. Review Decision
Based on findings, either:
- Auto-approve (if enabled and clean)
- Present findings to user for decision
- Provide approve/comment/request-changes options
Parameters
<pr-number>: Required - PR to review--fix-issues: Automatically correct found problems--auto-approve: Auto-approve if no critical issues--functional-tests: Enable functional testing
Example Usage
/flow:devflow-review-pr 123
/flow:devflow-review-pr 456 --fix-issues
/flow:devflow-review-pr 789 --auto-approve
Output
Complete review report:
๐ COMPLETE REVIEW - PR #123
๐ Implemented issue: #456 โ
๐ง Technical validations: โ
4/4 passing
๐ Coverage: 94% (+2% vs baseline)
๐งช Functional tests: โ
All passed
โ
Ready for merge
Source
git clone https://github.com/docutray/docutray-claude-code-plugins/blob/main/.kimi/skills/devflow-review-pr/SKILL.mdView on GitHub Overview
DevFlow: Pull Request Review Flow performs a complete technical review of PRs, including branch checkout, dependency setup, validations, auto-fix, and quality approval. It fetches PR data, analyzes changed files, runs validations, and guides the user to approve or request changes.
How This Skill Works
The flow fetches PR info from GitHub, identifies the linked issue, and analyzes modified files. It checks out the PR branch, installs dependencies, runs a full validation suite (tests, linting, type checks, build), and optionally auto-fixes issues. If functional tests are configured, it runs them and then presents findings for a final decision.
When to Use It
- You need to review a PR technically before merge.
- You want to validate PR quality and test changes in a clean environment.
- You need to check out and test PR changes, including forks.
- You want to auto-fix certain issues or auto-approve if the PR is clean.
- You want to review findings and decide to approve, comment, or request changes.
Quick Start
- Step 1: Run /flow:devflow-review-pr <pr-number> with optional flags.
- Step 2: Include --fix-issues or --auto-approve as needed.
- Step 3: Review the complete report and proceed with approval, comments, or changes.
Best Practices
- Fetch PR details from GitHub and identify the linked issue for context.
- Checkout the PR branch (including fork handling) and ensure a clean test environment.
- Run the full technical validation suite: tests, linting, type checks, and build.
- Enable auto-fix (--fix-issues) to automatically correct issues and re-validate.
- Capture evidence from functional tests and classify findings by severity before deciding.
Example Use Cases
- /flow:devflow-review-pr 123
- /flow:devflow-review-pr 456 --fix-issues
- /flow:devflow-review-pr 789 --auto-approve
- Review PRs with functional tests enabled as described in .claude/details/commands/review-pr.md
- Review a forked PR and validate changes in a CI-safe local environment