PR 审查 Enforcer
- 作者仓库星标 1
- 作者仓库 claude-skills
Pr Review Enforcer
Overview
Review code with a findings-first mindset instead of a summary-first mindset.
Core Workflow
- Read the diff and the surrounding code before judging the change.
- Look for correctness issues first: regressions, edge cases, state handling, concurrency, data integrity, and compatibility.
- Check architecture and maintainability: layering, ownership boundaries, duplication, naming, and hidden complexity.
- Check safety gaps: missing tests, weak observability, migrations, rollout risk, secrets, and authorization concerns.
- Report findings in priority order with file references and concise reasoning.
Deliver
- Lead with actionable findings, ordered by severity.
- Include open questions only after concrete issues.
- Mention testing gaps and residual risk even when the diff looks sound.
- State explicitly when no findings are discovered.
Guardrails
- Avoid generic praise or style-only comments unless they affect clarity or risk.
- Do not review from the diff alone when nearby code changes the meaning.
- Keep comments specific enough that the author can act on them quickly.
- 流狐分类
- 安全
- 作者声明 Agent
- 未找到明确声明；不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描，不代表运行安全
- 作者 / 版本 / 许可
- @00PrabalK00 · 未声明 license
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 即装即用
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无（仅作为资料）
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。Review code with a findings-first mindset instead of a summary-first mindset.
Read the diff and the surrounding code before judging the change. Look for correctness issues first: regressions, edge cases, state handling, concurrency, data integrity, and compatibility. Check architecture and maintainability: layering, ownership…
Lead with actionable findings, ordered by severity. Include open questions only after concrete issues. Mention testing gaps and residual risk even when the diff looks sound.
Avoid generic praise or style-only comments unless they affect clarity or risk. Do not review from the diff alone when nearby code changes the meaning. Keep comments specific enough that the author can act on them quickly.
# Pr Review Enforcer
## Overview
Review code with a findings-first mindset instead of a summary-first mindset.
## Core Workflow
1. Read the diff and the surrounding code before judging the change.
2. Look for correctness issues first: regressions, edge cases, state handling, concurrency, data integrity, and compatibility.
3. Check architecture and maintainability: layering, ownership boundaries, duplication, naming, and hidden complexity.
4. Check safety gaps: missing tests, weak observability, migrations, rollout risk, secrets, and authorization concerns.
5. Report findings in priority order with file references and concise reasoning.
## Deliver
- Lead with actionable findings, ordered by severity.
- Include open questions only after concrete issues.
- Mention testing gaps and residual risk even when the diff looks sound.
- State explicitly when no findings are discovered.
## Guardrails
- Avoid generic praise or style-only comments unless they affect clarity or risk.
- Do not review from the diff alone when nearby code changes the meaning.
- Keep comments specific enough that the author can act on them quickly.作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。
章节 -> Overview → Core Workflow → Deliver → Guardrails
要点 -> Review code with a findings-first mindset instead of a summary-first mindset. · 1. Read the diff and the surrounding code before judging the change. · - Lead with actionable findings, ordered by severity. · - Avoid generic praise or style-only comments unless they affect clarity or risk.
文件/命令 -> 原文未列出明确文件或命令
内容 SHA-256 -> 65d62c00df09
方法与流程
适用与边界
原文中的明确线索