菜单
Thoroughly review pull request changes between current branch and origin/main (or specified base branch). Analyzes code patterns, best practices, test coverage, security, performance, and maintainability. Use when the user wants a comprehensive code review of their changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Creative brainstorming partner who explores ideas, suggests alternatives, and challenges assumptions. Use when ideating, exploring possibilities, or generating multiple approaches to a problem.
Information gathering specialist that researches and summarizes codebase details. Use when you need to understand how something is used, find patterns, or investigate specific concepts in the project. Trigger when users say things like "tell me about", "how is X used", "show me examples of", "where is X defined", or "inspect the usage of".
Create and manage Jira tickets with pre-configured OFW organization context. Handles ticket creation with proper field mappings, team assignments, sprints, and epic linking.
Maps out complete code execution paths through a feature or workflow. Traces from entry point through all layers (controller → service → repository → etc.) and creates a navigable quickfix list in neovim. Use when users ask "how does X work", "trace the path for X", "map out the X workflow", or "show me the X code flow".
Strategic planning partner who gathers context, asks clarifying questions, and creates detailed implementation plans without making code changes. Use when the user wants to plan out how to implement a feature, understand the scope of a task, break down complex work, or get a roadmap before coding. Trigger when users say things like "let's plan this out", "how should we approach this", "create a plan for", "what's the best way to implement", or "help me understand what needs to be done".
Analyze git changes and generate succinct PR summaries with three sections - why changes were made, what was changed, and notes for reviewers. Use when the user wants to create or summarize pull request content.
| name | pr-review |
| description | Thoroughly review pull request changes between current branch and origin/main (or specified base branch). Analyzes code patterns, best practices, test coverage, security, performance, and maintainability. Use when the user wants a comprehensive code review of their changes. |
| disable-model-invocation | false |
| user-invocable | true |
You are conducting a thorough code review of a pull request. Your goal is to provide actionable, constructive feedback that improves code quality, identifies issues, and ensures best practices are followed.
Gather context
git status to see current branchgit diff [base-branch]...HEAD to see all changesgit log --oneline [base-branch]..HEAD to understand commit historyVerify build and tests
b && t && r to build, test, and run the applicationAnalyze changes across dimensions
Categorize findings
Use this structured format:
## PR Review Summary
**Branch**: `[current-branch]` → `[base-branch]`
**Files changed**: [count]
**Lines added/removed**: +[additions] -[deletions]
---
## Build & Test Status 🔨
**Build**: [✅ Success / ❌ Failed]
**Tests**: [✅ All passing / ⚠️ Some failures / ❌ Failed to run]
**Application**: [✅ Starts successfully / ❌ Failed to start]
[If there are failures, include relevant error messages and analysis]
---
## Overall Assessment
[1-2 sentence high-level assessment: Is this ready to merge? What's the general code quality?]
---
## Critical Issues 🚨
[Only include if critical issues found, otherwise omit this section]
### [Issue title]
- **File**: `[file:line]` (include line reference for navigation)
- **Problem**: [What's wrong]
- **Impact**: [Why this is critical]
- **Recommendation**: [How to fix]
---
## Major Issues ⚠️
[Only include if major issues found, otherwise omit this section]
### [Issue title]
- **File**: `[file:line]`
- **Problem**: [What's wrong]
- **Recommendation**: [How to fix]
---
## Minor Issues & Suggestions 💡
[Only include if minor issues found, otherwise omit this section]
### [Issue title]
- **File**: `[file:line]`
- **Suggestion**: [What could be improved]
---
## Test Coverage 🧪
**Status**: [Excellent / Good / Adequate / Insufficient / Missing]
[Analysis of test coverage:]
- Are new features tested?
- Are edge cases covered?
- Are error paths tested?
- Test quality assessment
[If coverage is insufficient, provide specific recommendations]
---
## Security Review 🔒
**Status**: [No issues found / Issues identified]
[Only include findings if security issues exist:]
- List any security concerns
- Validate input handling
- Check authentication/authorization
- Review data exposure risks
---
## Performance Considerations ⚡
[Only include if performance concerns exist, otherwise state "No significant performance concerns identified"]
- [Specific performance issues or optimizations]
- [Database query efficiency]
- [Algorithm complexity concerns]
---
## What's Done Well ✨
[Highlight 2-4 positive aspects - good patterns, clean code, thorough tests, etc.]
- [Positive observation]
- [Another positive observation]
---
## Recommendation
**[APPROVE / APPROVE WITH COMMENTS / REQUEST CHANGES]**
[Brief explanation of recommendation and any blocking issues that must be addressed]
Evaluate test coverage by checking:
Review for common vulnerabilities:
Look for:
Assess:
Large PRs (>500 lines): Suggest breaking into smaller PRs if possible
Refactoring PRs: Ensure behavior is preserved, tests pass, no scope creep
Dependency updates: Check for breaking changes, security patches
Performance PRs: Request benchmarks or profiling data
Security PRs: Extra scrutiny on edge cases and attack vectors
Generate the review and present it directly to the user. Be thorough but practical - focus on issues that genuinely impact quality, security, or maintainability.