菜单
Read-only review of an open pull request: scope, FSD layout, coding conventions, hygiene, tests, and PR body. Post findings as a GitHub PR comment. Use when a PR is opened or when asked to review a PR.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Periodic code health checkup for design drift not caught by CI. Use at version bumps or when asked for a code health check / 健康診断 / 健診. Audits logged advisory deviations and runs a deepen-modules pass.
Perform a project release: bump the semver `version` in package.json, summarize changes since the last release, and hand off to the health-checkup. Use when cutting a release, bumping the project version, or asked to "version up".
Project coding conventions and architecture constraints. Use when implementing, creating, or modifying components and modules (e.g. "create a component", "implement this feature").
Create a PR aligned with the AI-led workflow: summary, design (when relevant), impact and risks. Use when creating a pull request, opening a PR, pushing for review, or completing implementation of an issue.
Triage GitHub PR review feedback (top-level, inline, threads); implement agreed items; escalate disagreements or questions. Includes lint/test checks, per-thread replies with commit SHA, and a chat summary. Use when fixing review feedback on an open PR—not for greenfield implementation only.
Propose codifying reusable lessons from trial-and-error or explicit user requests into lint, rules, or skills. Use near task completion after failed first attempts, or when the user asks to "make it a rule" or "leave a lesson". NOT for empirically testing instructions on fresh agents (tune-prompt) or drafting a new skill without a lesson to codify.
| name | review-pull-request |
| description | Read-only review of an open pull request: scope, FSD layout, coding conventions, hygiene, tests, and PR body. Post findings as a GitHub PR comment. Use when a PR is opened or when asked to review a PR. |
Audit only. Do not edit code, commit, or merge.
Triggered automatically when a PR is opened (Cursor Automation) or on request.
gh pr view <N> --json number,title,body,headRefName,baseRefName,urlgh pr diff <N>Closes #XX / Refs #XX), read it: gh issue view <N>gh pr comment <N>).project-structure skill — FSD layers, slice layout, Public API via index.tscoding-guide skill — kebab-case, design tokens, design-system usageself-review)index.ts; no deep imports past the barrelconsole.log, debugger, dead commented code)TODO / FIXME without justification?., unused imports/exports, import type where appropriatePost this as the PR comment:
## PR review
### Must fix
- [file:line] issue — why it matters
### Suggestions
- [file:line] optional improvement
### Scope / PR body
- gaps or mismatches with the linked issue
### Clean
- No blocking issues found
Write "None" for empty sections.