菜单
Performs a structured PR review covering security, code quality, architecture consistency, and style. Outputs inline comments, a severity-rated checklist, and a summary with suggested fixes. Use when asked to review a PR, code review, check a pull request, or audit changes for TravelBookings .NET 8 backend or React 18 frontend code.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Execute a unit of work end-to-end: plan, implement, validate with typecheck and tests, then commit. Use when user wants to do work, build a feature, fix a bug, or implement a phase from a plan.
Explore a codebase to find opportunities for architectural improvement, focusing on deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
Guides end-to-end migration of a React SPA to Angular, covering codebase analysis, pattern mapping, file-by-file conversion, and validation. Use when user wants to migrate React to Angular, convert a React app, port React components to Angular, or restructure a React codebase into Angular.
| name | review-pr |
| description | Performs a structured PR review covering security, code quality, architecture consistency, and style. Outputs inline comments, a severity-rated checklist, and a summary with suggested fixes. Use when asked to review a PR, code review, check a pull request, or audit changes for TravelBookings .NET 8 backend or React 18 frontend code. |
/review-pr <PR number or branch>
Fetches diff, runs all review dimensions, outputs structured feedback.
gh pr diff <number> or git diff main...<branch>| Dimension | What to check |
|---|---|
| Security | Input validation, auth enforcement, secrets in code, SQL injection, XSS |
| Code Quality | Null handling, error paths, test coverage, dead code, logging |
| Architecture | Bounded context leakage, Outbox usage, Saga state machine correctness, ACL for Payment |
| Frontend conventions | See REFERENCE.md |
| Style | Naming, file structure, Clean Architecture layer violations |
Inline comments — one per issue, cite file + line:
src/Services/TravelBooking/Application/Commands/BookTripCommand.cs:42
[HIGH] Direct Service Bus publish bypasses Outbox — use OutboxPublisher instead.
Fix: Replace `_serviceBus.PublishAsync(...)` with `_outbox.AddMessageAsync(...)`.
Severity checklist at the end:
## Review Summary
### 🔴 HIGH (must fix before merge)
- [ ] BookTripCommand.cs:42 — Direct Service Bus publish bypasses Outbox
### 🟡 MEDIUM (should fix)
- [ ] PaymentService.cs:18 — Missing cancellation token propagation
### 🟢 LOW (consider fixing)
- [ ] BookingController.cs:5 — Unused using directive
Overall verdict: APPROVE / REQUEST CHANGES / COMMENT
For each HIGH/MEDIUM issue, provide a concrete fix snippet, not just a description.
| Level | Meaning |
|---|---|
| HIGH | Security risk, data loss, broken contract, pattern violation that will cause bugs |
| MEDIUM | Correctness concern, missing test, tech debt that compounds quickly |
| LOW | Style, naming, minor cleanup |
See REFERENCE.md for TravelBookings-specific pattern rules.