菜单
Fetch and review a GitHub pull request with comprehensive analysis — pattern consistency against existing codebase, junior-friendly explanations, documentation links, manual testing steps with edge cases, and Fix Verification Criteria. Requires gh CLI. Usage: /skill:pr-review <PR URL or number>
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/aaronmaturen/pi-config --skill pr-review命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | pr-review |
| description | Fetch and review a GitHub pull request with comprehensive analysis — pattern consistency against existing codebase, junior-friendly explanations, documentation links, manual testing steps with edge cases, and Fix Verification Criteria. Requires gh CLI. Usage: /skill:pr-review <PR URL or number> |
Review a GitHub PR and provide a comprehensive summary with documentation links.
PR URL: $ARGUMENTS
Parse PR Information
https://github.com/{owner}/{repo}/pull/{number}Setup PR for Review
git stash push -m "PR review backup"git branch --show-current > .pr-review-original-branchgh pr checkout {number} --repo {owner}/{repo}git diff {original-branch}...HEAD -- package.json requirements.txt Gemfile go.modFetch PR Overview
gh pr view {number} --repo {owner}/{repo} --json title,body,state,author,createdAt,files,additions,deletionsgh pr diff {number} --repo {owner}/{repo} - Get the full diffAnalyze Changed Files
Search Existing Codebase for similar implementations:
Compare PR Patterns with established ones:
Examples to Look For:
Create Junior-Friendly Summary
For each significant change:
Documentation Research
# Check package version for accurate docs URL
cat package.json | grep '"<library>"'
Learning Points
Testing Strategy
Manual Testing Steps:
Data Setup Requirements:
Edge Cases to Test:
Test Data Examples:
// Example user for testing auth
{
"email": "test@example.com",
"password": "TestPass123!",
"role": "admin"
}
Questions to Ask
# PR Review: Add User Authentication (#123)
## Overview
This PR adds JWT-based authentication to our API. It affects 15 files
and introduces middleware for protecting routes.
## Key Changes Explained
### 1. Authentication Middleware (auth.middleware.ts)
**What**: New file that checks if requests have valid JWT tokens
**Why**: We need to protect sensitive API endpoints
**How**:
- Extracts token from Authorization header
- Verifies token signature
- Attaches user info to request
📚 JWT Documentation: https://jwt.io/introduction
### 2. User Model Updates (user.model.ts)
**What**: Added password hashing methods
**Why**: Never store plain text passwords
**How**: Uses bcrypt to hash passwords before saving
📚 Password Hashing Best Practices: https://auth0.com/blog/hashing-passwords-one-way-road-to-security/
## Pattern Consistency Analysis
### ✅ Follows Existing Patterns:
- **Error Handling**: Uses established `AppError` class from `src/utils/errors.ts`
- **Response Format**: Matches existing API response structure `{ data, status, message }`
- **Middleware Pattern**: Consistent with existing middleware in `src/middleware/`
### ⚠️ Modified Patterns:
- **JWT Storage**: Changed from localStorage to httpOnly cookies (Security improvement)
- Justification: Prevents XSS attacks
### ❌ New Patterns Introduced:
- **Token Refresh**: Added refresh token rotation
- Justification: No existing refresh mechanism found
- Consider: Should align with planned OAuth implementation
## Testing Instructions
### Data Setup
1. Create test database with:
```sql
INSERT INTO users (email, password_hash, role) VALUES
('admin@test.com', '$2b$10$...', 'admin'),
('user@test.com', '$2b$10$...', 'user');
JWT_SECRET=test-secret-key
JWT_EXPIRY=1h
# If using Docker:
docker-compose up -d
docker-compose exec app npm install # Install any new dependencies
# If not using Docker:
npm install # or yarn install
npm run db:migrate # Run any new migrations
Test Login Flow:
Test Protected Routes:
## Cleanup (After Review Complete):
```bash
# When ready to return to original work:
git checkout $(cat .pr-review-original-branch)
# Restore stashed work
git stash pop
# Clean up
rm .pr-review-original-branch
# Optionally delete PR branch locally
git branch -D pr-branch-name
Note: Stay on the PR branch while reviewing and testing. Only run cleanup when completely done.
gh) to be installed and authenticatedInvestigate a technical spike by gathering requirements interactively, analyzing the codebase with grep and read tools, researching libraries and technologies, evaluating options, and producing a structured report with a high-level proposals doc (for managers/PMs/designers) and detailed technical analysis. Uses Monte Carlo simulation for timeline forecasting with confidence levels. Optionally integrates with JIRA if a ticket ID is referenced.
Investigate a bug using the 5 Whys root cause analysis technique. Fetches ticket details from JIRA (if a ticket ID is provided), checks for previous investigation reports, defines Fix Verification Criteria before digging in, traces the bug across frontend and backend repos, and generates a structured investigation report with timeline and recommendations. Requires jira CLI if using a ticket ID.
Investigate and plan implementation of a new feature using Acceptance Criteria as the central organizing principle. Fetches ticket details from JIRA, validates and clarifies AC before any planning begins, maps every implementation task back to a specific AC, and generates an implementation plan, technical design, task breakdown, and PR checklist template. Requires jira CLI.