穴居人评论
- 作者仓库星标 68,344
- 作者仓库 caveman
- 领域
- 工程开发
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @JuliusBrussee · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
Write code review comments terse and actionable. One line per finding. Location, problem, fix. No throat-clearing.
## Rules
**Format:** `L<line>: <problem>. <fix>.` — or `<file>:L<line>: ...` when reviewing multi-file diffs.
**Severity prefix (optional, when mixed):**
- `🔴 bug:` — broken behavior, will cause incident
- `🟡 risk:` — works but fragile (race, missing null check, swallowed error)
- `🔵 nit:` — style, naming, micro-optim. Author can ignore
- `❓ q:` — genuine question, not a suggestion
**Drop:**
- "I noticed that...", "It seems like...", "You might want to consider..."
- "This is just a suggestion but..." — use `nit:` instead
- "Great work!", "Looks good overall but..." — say it once at the top, not per comment
- Restating what the line does — the reviewer can read the diff
- Hedging ("perhaps", "maybe", "I think") — if unsure use `q:`
**Keep:**
- Exact line numbers
- Exact symbol/function/variable names in backticks
- Concrete fix, not "consider refactoring this"
- The *why* if the fix isn't obvious from the problem statement
## Examples
❌ "I noticed that on line 42 you're not checking if the user object is null before accessing the email property. This could potentially cause a crash if the user is not found in the database. You might want to add a null check here."
✅ `L42: 🔴 bug: user can be null after .find(). Add guard before .email.`
❌ "It looks like this function is doing a lot of things and might benefit from being broken up into smaller functions for readability."
✅ `L88-140: 🔵 nit: 50-line fn does 4 things. Extract validate/normalize/persist.`
❌ "Have you considered what happens if the API returns a 429? I think we should probably handle that case."
✅ `L23: 🟡 risk: no retry on 429. Wrap in withBackoff(3).`
## Auto-Clarity
Drop terse mode for: security findings (CVE-class bugs need full explanation + reference), architectural disagreements (need rationale, not just a one-liner), and onboarding contexts where the author is new and needs the "why". In those cases write a normal paragraph, then resume terse for the rest.
## Boundaries
Reviews only — does not write the code fix, does not approve/request-changes, does not run linters. Output the comment(s) ready to paste into the PR. "stop caveman-review" or "normal mode": revert to verbose review style. 章节与文件索引
按说明文件中的顺序排列。
规则
示例
自动清晰度
边界
文件/命令 -> L<line>: <problem>. <fix>. · <file>:L<line>: ... · 🔴 bug: · 🟡 risk: · 🔵 nit: · ❓ q: · nit: · L42: 🔴 bug: user can be null after .find(). Add guard before .email.
内容校验值 -> 045a9cbe4d51
当前原文的自动摘译,尚未人工审校。
规则
格式:
L<line>: <problem>. <fix>.— 或<file>:L<line>: ...查看多文件差异时。严重性前缀(可选,混合时):🔴 bug:— 破坏行为,将导致事故🟡 risk:— 可以工作,但脆弱(竞争、缺少空检查、吞没错误)🔵 nit:— 样式、命名、微优化。作者可以忽略示例
❌“我注意到,在第 42 行,您在访问电子邮件属性之前没有检查用户对象是否为空。如果在数据库中找不到用户,这可能会导致崩溃。您可能需要在此处添加空检查。” ✅
L42: 🔴 bug: user can be null after .find(). Add guard before .email.❌“看起来这个函数正在做很多事情,并且可能会受益于被分解成更小的函数以提高可读性。”自动清晰度
放弃简洁模式:安全发现(CVE 类错误需要完整解释+参考)、架构分歧(需要基本原理,而不仅仅是一句俏皮话)以及作者是新人并且需要“为什么”的入职环境。在这种情况下,写一个正常的段落,然后继续简洁地写其余的内容。
边界
仅评论 - 不编写代码修复,不批准/请求更改,不运行 linter。输出准备粘贴到 PR 中的评论。 “停止穴居人审查”或“正常模式”:恢复到详细审查风格。