메뉴
Use when the user explicitly requests review of a PR, diff, branch, commit range, merge readiness, or review feedback, or when a high-risk change has reached an explicit pre-integration review gate; do not trigger merely because ordinary development finished.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when a user message needs Chinese-first intent inference, low-confidence collaborative clarification, routing, workflow weight control, skill choice, review/testing/planning/debugging/evaluation routing, proactive multi-thread collaboration or conflict coordination, continuation handling, execution permission inference, or protection from process over-escalation.
Use when active development or explicit refactoring has concrete code-structure risk: a source file is accumulating independently changing responsibilities, a class/component/function is hard to navigate or test, repeated changes touch distant sections, or the user asks to split a giant file; do not use for line count alone, generated/vendor/migration/schema/fixture files, or cohesive modules that remain easier to maintain together.
Use when the user explicitly enables an automated same-project multi-thread development loop that keeps peer Codex tasks progressing, recovers conflicts or stale coordination, integrates verified work into local main, and closes cleanup without repeated gates; do not use before opt-in, for one-off coordination, remote publication without permission, or subagent creation.
Use when existing independent Codex App threads work in the same project and need peer advice, collaboration proposals, shared progress awareness, ownership arbitration, conflict pause/resume, discussion, merge coordination, status exchange, or handoff through native thread tools without creating subagents.
Use when a verified or integrated software change has concrete temporary artifacts, generated noise, stale claims, merged local branches, or disposable worktrees to clean, or when the user explicitly asks to remove development residue or old branches.
Use when the user or project rules explicitly request project-local memory/dashboard initialization or updates, or when an existing `.docs/project-memory/` is needed for cross-session recovery, durable decisions, blockers, parallel-agent coordination, or formal handoff; do not auto-initialize or sync it for ordinary development.
| name | ccdawn-pr-review |
| description | Use when the user explicitly requests review of a PR, diff, branch, commit range, merge readiness, or review feedback, or when a high-risk change has reached an explicit pre-integration review gate; do not trigger merely because ordinary development finished. |
| license | MIT |
只读审阅 PR、diff、branch 或 commit range，判断需求覆盖、回归风险和 merge readiness。先给 findings，不用长矩阵掩盖结论；审阅阶段不顺手改代码。
ccdawn-bug-review、ccdawn-performance-engineering、ccdawn-planning、ccdawn-brt、提交/PR/合并准备或 BLOCKED。ccdawn-brt 或更具体 owner，复合任务不吞其他 owner。下一步建议: <一个具体动作>。明显 N+1、循环 I/O、重复全量计算或无界资源增长可用结构/确定性计数形成 finding；声称“更快/回归”必须有可比较 baseline。需要实际 profiling 或 before/after 时以本 skill 为 primary、ccdawn-performance-engineering 为 support，不把每个 PR 变成性能审计。
P0 BLOCKER：数据丢失、安全事故、核心不可用或不可逆发布风险。P1 MUST_FIX：重要需求缺失、明确 bug、关键契约/测试/迁移风险。P2 SHOULD_FIX：边界、错误处理、维护性或局部回归风险。P3 NICE_TO_HAVE：默认省略；只有能明显降低近期误改或审阅成本时才保留。每条包含紧凑文件/行号或 diff 位置、问题、影响、建议方向和验证条件。纯风格偏好、无行为影响的命名建议、未被 diff 影响的既有问题不作为 finding；必要时用一句非阻塞备注。没有问题时明确“未发现阻塞性问题”，并说明尚未覆盖的证据边界。
多个问题按依赖和修复成本给执行顺序；用户已要求修复 review findings 时，回最具体 owner 连续处理所有 SAFE_DIRECT 项，不每项询问。设计分叉、高风险动作或 BLOCKED 才暂停。
READY：无 P0/P1，需求与证据足够。READY_WITH_FIXES：仅有非阻塞 P2/P3。READY_CONDITIONAL：变更相关证据通过，但仓库 gate 因已在 base 复现的 BASELINE_FAILURE 或与 diff 无关的 ENVIRONMENT_FAILURE 不可运行；必须记录失败命令、base 复现、已通过证据和集成后补验责任。NEEDS_CHANGES：存在 P0/P1、需求偏离或关键证据缺失。BLOCKED：没有可审 diff，或审查目标/证据无法取得。gate 失败先分为 CHANGE_FAILURE / BASELINE_FAILURE / ENVIRONMENT_FAILURE / POLICY_FAILURE / UNKNOWN。只做一次限时环境 probe；无新信号就停止安装或重建环境。未在干净 base/等价事实源复现的失败不能称为 baseline。安全、secret、权限、数据迁移、发布合规及项目明确不可绕过的 gate 不允许条件通过。
Findings:
- P0/P1/P2/P3 [文件:行] 问题；影响；建议；验证条件
结论: READY / READY_WITH_FIXES / READY_CONDITIONAL / NEEDS_CHANGES / BLOCKED
审阅范围与需求来源: ...
验证证据/缺口: ...
执行顺序（仅多个修复项时）: ...
剩余风险: ...
下一步建议: <一个具体动作>
实际提交、推送、合并和发布仍需对应权限；审阅结论不等于自动执行远程动作。