技能审查回复
- 作者仓库星标 3,406
- 作者仓库 claude-octopus
- 领域
- 工程开发
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @nyldn · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.
> Cross-reference commands use installed skill names in Codex rather than `/octo:*` slash commands.
> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.
> For host tool equivalents, see `skills/blocks/codex-host-adapter.md`.
# Receiving Code Review
## Core Principle
Code review requires technical evaluation, not performative agreement.
**Never blindly implement review feedback.** Verify it's correct for THIS codebase before changing anything.
## The Response Pattern
```
WHEN receiving code review feedback:
1. READ — Complete feedback without reacting
2. RESTATE — Summarize the requirement in your own words
3. VERIFY — Check against actual codebase state
4. EVALUATE — Is this technically sound for THIS context?
5. RESPOND — Technical acknowledgment OR reasoned pushback
6. IMPLEMENT — One item at a time, verify each change
```
## Forbidden Responses
**NEVER say:**
- "You're absolutely right!" (without verification)
- "Great catch!" (before confirming it IS a catch)
- "I'll fix that right away!" (before evaluating whether it needs fixing)
- "Done!" (without running verification — see skill-verification-gate)
**These are social performance, not technical evaluation.** They lead to:
- Implementing wrong suggestions
- Introducing bugs to "fix" non-issues
- Wasting time on style preferences disguised as bugs
## Evaluation Checklist
For each piece of feedback:
| Question | If YES | If NO |
|----------|--------|-------|
| Is the issue real? (verify in code) | Continue evaluation | Push back with evidence |
| Does the suggested fix work here? | Continue evaluation | Propose alternative |
| Does fixing this break something else? | Fix both or push back | Implement the fix |
| Is this a style preference or a real problem? | Acknowledge, deprioritize | Fix it |
| Was this already considered and rejected? | Explain the trade-off | Implement |
## How to Push Back
When feedback is wrong or doesn't apply:
```markdown
> Reviewer: "This function should handle null input"
>
> Response: "Checked — this function is only called from `processUser()`
> (line 47) which validates non-null before dispatch. Adding null handling
> here would be dead code. The caller contract guarantees non-null."
```
Provide:
1. What you checked
2. Why the suggestion doesn't apply
3. Evidence (line numbers, call sites, tests)
## Multi-Provider Review Context
In Claude Octopus workflows, review feedback comes from multiple sources:
- **Codex review** — tends toward enterprise patterns, may over-engineer
- **Gemini review** — tends toward ecosystem conformity, may suggest unnecessary deps
- **Claude review** — tends toward elegance, may under-engineer error handling
- **Sonnet review** — tends toward thoroughness, may flag low-priority issues
When providers disagree:
- Check which provider's suggestion matches the ACTUAL codebase conventions
- The codebase's existing patterns win over any provider's preferences
- If two providers flag the same issue, it's probably real
## Handling Feedback Loops
When a reviewer flags an issue and you fix it:
1. Make the fix
2. **Run verification** (skill-verification-gate) — prove the fix works
3. **Re-read the original feedback** — did you address the root cause or just the symptom?
4. If the reviewer re-reviews and finds new issues, that's normal — don't get frustrated
5. Each round should have FEWER issues, not different ones
If the same issue keeps coming back:
- You're fixing symptoms, not the root cause
- Stop and re-read the feedback from scratch
- Ask the reviewer to clarify if the issue is ambiguous
## When Review Feedback Conflicts with Requirements
If a reviewer suggests something that contradicts the spec/requirements:
1. Note the conflict explicitly
2. Check if the spec is wrong (it might be)
3. If spec is correct: implement the spec, note the reviewer's concern for future consideration
4. If spec is wrong: flag to the user before changing anything
**Requirements trump review suggestions. User intent trumps both.**
章节与文件索引
按说明文件中的顺序排列。
核心原则
禁止回应
评估清单
如何反击
多提供商审查环境
文件/命令 -> /octo:* · skills/blocks/codex-host-adapter.md · processUser() · spec/requirements
内容校验值 -> d8bb42a7addd
当前原文的自动摘译,尚未人工审校。
核心原则
代码审查需要技术评估,而不是执行协议。切勿盲目落实审核反馈。在更改任何内容之前,请验证此代码库的正确性。
禁止回应
永远不要说:“你完全正确!” (未经核实)“收获很大!” (在确认这是一个陷阱之前)“我会立即解决这个问题!” (在评估是否需要修复之前)“完成!” (不运行验证 - 请参阅技能验证门)
评估清单
对于每条反馈: 问题 · 如果是 · 如果否 该问题是否真实? (在代码中验证)·继续评估·用证据反驳建议的修复在这里有效吗? · 继续评估 · 提出替代方案 修复此问题是否会破坏其他内容? · 修复两者或推迟 · 实施修复
如何反击
当反馈错误或不适用时: 提供: 您检查的内容 为什么建议不适用 证据(线路号码、呼叫站点、测试)
多提供商审查环境
在 Claude Octopus 工作流程中,审核反馈来自多个来源: Codex 审核 - 倾向于企业模式,可能过度设计 Gemini 审核 - 倾向于生态系统整合,可能建议不必要的部门 Claude 审核 - 倾向于优雅,可能设计不足 Sonnet 审核 - 倾向于彻底性,可能标记低优先级问题