القائمة
Review pull requests. Read-only analysis — does NOT modify code, build, deploy, or run tests. Use when: review PR, code review, check branch changes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | pr-review |
| description | Review pull requests. Read-only analysis — does NOT modify code, build, deploy, or run tests. Use when: review PR, code review, check branch changes. |
Do NOT trust the developer's completion summary in PR comments. You MUST:
This rule is BLOCKING — violating it means approving changes you haven't verified, which defeats the purpose of review.
Evaluate every change against the following criteria:
coding-principles skill):
Categorize each finding by severity:
For each finding, use this format:
**[SEVERITY]** `file:line` — description
Suggestion: how to fix
Development workflow - branching, fix/feature flow, release process, version bump, commit conventions. Use when: planning development work, creating branches, merging, preparing releases, bumping version, updating changelog.
Process invoices from messages (PDF/image attachments or URLs). Extract key values, validate mandatory fields, organize by month, update Excel. Use when: receiving invoices, processing receipts, bookkeeping tasks.
Incremental development methodology - small step iteration with validation. Use when: implementing features, fixing bugs, making code changes, planning implementation. 渐进式小步迭代开发方法。
Expert UI/UX/Frontend engineer agent. Covers UX heuristics, design systems, accessibility (WCAG 2.2), CSS architecture, design tokens, typography, color theory, motion design, responsive design, Core Web Vitals performance, modern frontend architecture, design-to-code workflow, and testing. Use when building UI, reviewing designs, optimizing frontend performance, or making UX decisions.
Andrej Karpathy's 4 coding principles for LLM agents: Think Before Coding, Simplicity First, Surgical Changes, Goal-Driven Execution. Use when writing code, planning, or reviewing code to reduce common LLM coding mistakes.
Create structured implementation plans with incremental steps. Use when: in plan mode, creating implementation plans, analyzing requirements, proposing solutions.