Agent SkillsHashWarlock/nobody-plans-for-pi › nobody-receives-code-review

nobody-receives-code-review

GitHub

指导开发者在接收代码审查反馈时,通过理解、验证和评估等技术严谨步骤,基于证据做出同意、拒绝或澄清的响应,避免盲从或防御性反应。

skills/nobody-receives-code-review/SKILL.md HashWarlock/nobody-plans-for-pi

Trigger Scenarios

收到代码审查意见 需要回应技术建议

Install

npx skills add HashWarlock/nobody-plans-for-pi --skill nobody-receives-code-review -g -y
More Options

Use without installing

npx skills use HashWarlock/nobody-plans-for-pi@nobody-receives-code-review

指定 Agent (Claude Code)

npx skills add HashWarlock/nobody-plans-for-pi --skill nobody-receives-code-review -a claude-code -g -y

安装 repo 全部 skill

npx skills add HashWarlock/nobody-plans-for-pi --all -g -y

预览 repo 内 skill

npx skills add HashWarlock/nobody-plans-for-pi --list

SKILL.md

Frontmatter
{
    "name": "nobody-receives-code-review",
    "description": "Use when receiving code review feedback, before implementing suggestions — requires technical rigor and verification, not performative agreement"
}

Receiving Code Review

Overview

Code review feedback requires critical evaluation, not blind acceptance. Verify each suggestion technically before implementing.

The Rule

For each piece of feedback:

  1. Understand — What specifically is the concern?
  2. Verify — Is the concern technically valid? Check the code.
  3. Evaluate — Does the suggested fix actually address the concern?
  4. Respond — Agree with evidence, disagree with evidence, or ask for clarification

Response Types

Agree (with evidence)

You're right — line 42 doesn't handle the null case.
Fix: added null check with test in abc123.

Disagree (with evidence)

This is actually handled by the validation in middleware.py:30
which runs before this function is called. Here's the test
that covers it: test_middleware_validates_input.

Clarify

I'm not sure I understand the concern about the retry logic.
Are you worried about the backoff strategy or the max retries?

Anti-Patterns

Bad Good
"Good point, fixed!" (without checking) Verify the concern, then fix
Implementing all suggestions blindly Evaluate each on merit
Dismissing without explanation Provide evidence for disagreement
"I'll fix it later" Fix now or explain why not
Changing unrelated code during review Only address review feedback

Red Flags

  • Agreeing with everything without verification
  • Making changes you don't understand
  • Getting defensive instead of curious
  • Implementing suggestions that introduce new bugs
  • Not running tests after applying feedback

Version History

  • fc2edc0 Current 2026-07-25 05:06

Same Skill Collection

skills/nobody-brainstorms/SKILL.md
skills/nobody-debugs/SKILL.md
skills/nobody-executes-plans/SKILL.md
skills/nobody-finishes-a-development-branch/SKILL.md
skills/nobody-requests-code-review/SKILL.md
skills/nobody-uses-git-worktrees/SKILL.md
skills/nobody-uses-tdd/SKILL.md
skills/nobody-verifies-before-completion/SKILL.md
skills/nobody-writes-plans/SKILL.md
skills/nobody-writes-skills/SKILL.md
skills/using-plans-for-nobody/SKILL.md

Metadata

Files
0
Version
fc2edc0
Hash
a3a56cd4
Indexed
2026-07-25 05:06

ホーム - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-08-29 13:58
浙ICP备14020137号-1 $お客様$