القائمة
Use when retrieving or addressing PR review comments.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use BEFORE building or changing any UI — components, layout, color, spacing, typography, interaction states, or visual styling — to verify the planned change matches the Figma design via the Figma MCP. Run this gate before writing or editing UI code.
Use when placing features, repositories, hooks, or fixing dependency-cruiser errors.
Use when validating frontend changes before commit, push, or PR.
Use when placing, moving, naming, or splitting frontend files.
Use when frontend files, components, hooks, or helpers exceed complexity gates.
Use when creating new repository documentation or agent guides.
| name | code-review |
| description | Use when retrieving or addressing PR review comments. |
make pr-comments
make pr-comments PR=123
make pr-comments FORMAT=json
make pr-comments FORMAT=markdown
Resolve comments in priority order, then verify with formatting, focused tests, and the full lint gate.
| Type | Response |
|---|---|
| Committable suggestion | Apply if correct, then verify |
| Bug or regression | Reproduce and add or update a focused test |
| Architecture concern | Use code-organization or complexity-management |
| Test gap | Add coverage at the smallest meaningful level |
| Question | Answer directly or make the code clearer |
make format
make lint
Add focused suites when comments touch behavior:
make test-unit-client
make test-e2e
make test-visual
make pr-comments before finishing review work.Before applying this skill, confirm the active task against ../AI-AGENT-GUIDE.md and ../SKILL-DECISION-GUIDE.md so every relevant skill is consulted.
Before presenting changes, check changed text files for lines longer than 100 characters.
If any exist, tell the user each path:line and measured character count.
Treat this as disclosure, not failure, unless a project gate fails.