菜单
Repo-specific code review guidance for this repository. Only the categories declared overridable below may be specialized here; the review output schema, severity labels, safety rules, and evidence rules are defined by the review-pr skill.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Implement a fix or feature from a GitHub, Jira, Linear, or other issue-tracker issue by fetching issue context, inspecting the current codebase, making code changes, validating them, opening a GitHub pull request, and reporting progress back to the original issue.
Post a concise software-factory status update to a Slack channel via an incoming webhook after a factory phase completes a handoff. Use when a triage decision is made, a specs PR is opened, an implementation PR is opened, or an automated review verdict is published, and the SLACK_WEBHOOK_URL secret is configured.
Review a pull request diff and write structured feedback to review.json for the workflow to publish. Use when reviewing a checked-out PR from local artifacts like pr_diff.txt and pr_description.txt and producing machine-readable review output instead of posting directly to GitHub.
Audit a pull request diff for common security concerns (input validation, sanitization, authentication and authorization, secrets management, unsafe dependencies, and related risks) and fold findings into the same review.json produced by the base PR review. Use as a supplement to `review-pr` whenever a code PR is being reviewed.
Audit a product or tech spec pull request diff for high-level security concerns (threat surface, authentication and authorization model, trust boundaries, sensitive data handling, secrets and key management, dependency posture, and abuse or misuse cases) and fold findings into the same review.json produced by the base review. Use as a supplement to `review-pr` whenever a spec-only PR (changes limited to `specs/` or docs) is being reviewed.
Coordinate spec-driven development for a GitHub, Jira, Linear, or other issue-tracker issue moved to the Spec status (or given an equivalent label) by using write-product-spec and write-tech-spec, creating PRODUCT.md and TECH.md, opening a pull request, and routing the issue onward.
| name | review-pr-local |
| specializes | review-pr |
| description | Repo-specific code review guidance for this repository. Only the categories declared overridable below may be specialized here; the review output schema, severity labels, safety rules, and evidence rules are defined by the review-pr skill. |
This file is a companion to the core review-pr skill. It does not
redefine the review output schema, severity labels, safety rules,
evidence rules, suggestion-block constraints, or the annotated-diff
line contract. It only specializes the categories listed below.
Tailor this file to your team as your factory runs. The
improve-review-pr loop proposes evidence-backed additions here based
on how humans react to automated review comments, so repo conventions
accumulate in this file instead of diverging the core skill.
No repo-specific guidance has been captured yet. Add entries under the categories above as reviewer feedback accumulates.
