review-pr
- 作者仓库星标 0
- 作者更新于 2026年8月25日 07:09
- 作者仓库 skills
PR Review
Review the branch's change surface, not the whole repository.
- Establish the diff:
git diff <base>...HEAD(andgit diff <base>when the working tree carries uncommitted changes that belong to the branch). The base branch is named by the caller; fall back tomain. - Review every changed hunk for correctness: wrong results on edge inputs, unhandled error paths, and behavior that contradicts the function's name or callers.
- Check test coverage for the changed behavior: new logic without a test exercising its edge cases is a finding.
- Check documentation the diff made stale: statements in README or docs that were true on the base branch and are false after the change.
- Report every defect found, each with a severity; include minor and informational findings. Do not report defects in files the branch did not touch — they are outside the pull request.
- 流狐分类
- 工程开发
- 作者声明 Agent
- 未找到明确声明；不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描，不代表运行安全
- 作者 / 版本 / 许可
- @trailofbits · 未声明 license
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 即装即用
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无（仅作为资料）
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。 原文未拆分步骤
# PR Review Review the branch's change surface, not the whole repository. 1. Establish the diff: `git diff <base>...HEAD` (and `git diff <base>` when the working tree carries uncommitted changes that belong to the branch). The base branch is named by the caller; fall back to `main`. …
# PR Review
Review the branch's change surface, not the whole repository.
1. Establish the diff: `git diff <base>...HEAD` (and `git diff <base>` when the working
tree carries uncommitted changes that belong to the branch). The base branch is named
by the caller; fall back to `main`.
2. Review every changed hunk for correctness: wrong results on edge inputs, unhandled
error paths, and behavior that contradicts the function's name or callers.
3. Check test coverage for the changed behavior: new logic without a test exercising its
edge cases is a finding.
4. Check documentation the diff made stale: statements in README or docs that were true
on the base branch and are false after the change.
5. Report every defect found, each with a severity; include minor and informational
findings. Do not report defects in files the branch did not touch — they are outside
the pull request. 证据边界与执行链路
作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。
章节 -> 原文未使用二、三级标题
要点 -> Review the branch's change surface, not the whole repository.
文件/命令 -> git diff <base>...HEAD · git diff <base> · main
内容 SHA-256 -> 53d39b683ce2
原文结构
适用与边界
原文中的明确线索
git diff <base>...HEAD、git diff <base>、main