القائمة
Summarize changes in a pull request with structured analysis of what changed, why, and potential concerns. Use when asked to review a PR, summarize PR changes, or understand what a PR does.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Automatic quality control, linting, and static analysis procedures. Use when validating code changes for syntax correctness and project standards. Triggers on keywords: lint, format, check, validate, types, static analysis.
Refactoring and cleanup - improving code structure, removing dead code, eliminating duplication, or pre-merge cleanup. Use when code is hard to maintain, has dead code or debug artifacts, or needs pre-merge polishing.
Fix a GitHub issue end-to-end - from reading the issue, understanding requirements, implementing the fix, writing tests, and creating a commit. Use when given a GitHub issue number or URL to resolve.
Optimize code for readability, performance, maintainability, and security across Bash, Python, and Rust. Use when asked to improve code quality, optimize performance, add type safety, or refactor for idioms.
Create, debug, and optimize GitHub Actions workflows with security best practices. Use when asked to "create workflow", "fix workflow", "add CI", or needs help with GitHub Actions.
Review code changes (diffs, PRs, patches) and provide structured, actionable feedback on correctness, maintainability, and test coverage. Use when the user asks for a code review, requests feedback on a patch/PR, or wants an assessment of changes.
| name | pr-review |
| description | Summarize changes in a pull request with structured analysis of what changed, why, and potential concerns. Use when asked to review a PR, summarize PR changes, or understand what a PR does. |
| allowed-tools | Bash(gh *), Read, Glob, Grep |
Summarize and analyze the current pull request.
Collect PR data before analysis:
gh pr viewgh pr diffgh pr diff --name-onlygh pr view --commentsgh pr checksThink through the PR systematically:
Structure the summary as:
One paragraph describing what the PR does and why.
Group changes into logical categories with brief descriptions.
| Area | Files | Summary |
|---|---|---|
| Feature | src/auth/ | Added OAuth2 flow |
| Tests | tests/auth/ | Coverage for new auth |
| Config | .env.example | New OAuth env vars |
Notable implementation choices, trade-offs, or patterns used.
Overall assessment: ready to merge, needs changes, or needs discussion.
Overview: Fixes null pointer in UserService.getProfile() when user has no avatar set.
Changes: 1 file (src/services/user.ts), 1 test file
Key Decision: Returns default avatar URL instead of null
Concerns: None
Verdict: Ready to merge
Overview: Adds real-time notifications via WebSocket with Redis pub/sub backend.
Changes: 12 files across services, middleware, frontend, tests, and config
Key Decision: Chose Redis pub/sub over polling for scalability
Concerns: No load testing results, missing reconnection logic, new Redis dependency
Verdict: Needs changes - address reconnection handling before merge