القائمة
Code review best practices including review checklist, comment types, severity levels, feedback patterns, and PR size guidelines. Auto-loaded during code review.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
End-of-session routine. Ensures test coverage, performs self-review, runs validation, and commits cleanly. Use when finishing a unit of work.
Full feature implementation workflow with explore, plan, code, test, validate, and commit phases. Use for new features, enhancements, or significant code changes.
Iterate on an open PR until CI passes and all review feedback is addressed. Fetches status, categorizes findings by severity, applies fixes, and loops until clean.
Create a detailed implementation plan without writing code. Read-only analysis and planning with user approval gate. Use before implementing features or making significant changes.
Systematic security audit with confidence-based reporting. Analyzes attack surfaces, checks against OWASP categories, and reports only confirmed or likely vulnerabilities. Use for pre-merge security review or periodic audits.
Run validation checks to ensure code quality, security, and correctness. Supports quick (scoped), full (CI pipeline), fix (auto-correct), and CI mirror modes.
| name | code-review-guidelines |
| description | Code review best practices including review checklist, comment types, severity levels, feedback patterns, and PR size guidelines. Auto-loaded during code review. |
| category | protocol |
| user-invocable | false |
| Label | Meaning | Blocks PR? |
|---|---|---|
[blocking] | Must address before merge | Yes |
[suggestion] | Recommended improvement | No |
[nit] | Minor style issue | No |
[question] | Seeking clarification | No |
[praise] | Positive feedback | No |
Be specific:
**[suggestion]** The variable `d` on line 45 is unclear. Consider
renaming to `dateOfBirth` to indicate what date this represents.
Explain why:
**[blocking]** Using `any` here defeats type safety. This function
receives user input, so we need proper types.
Suggest alternatives:
**[suggestion]** This loop is O(n²). Consider using a Map for O(n).
Give praise:
**[praise]** Great implementation of retry logic with exponential backoff.
| Lines Changed | Assessment |
|---|---|
| < 100 | Excellent |
| 100-400 | Good |
| 400-800 | Consider splitting |
| > 800 | Should split |