AgentSkillsCN

critical-acceptance

当用户请求“评估这段反馈”“我是否应该接受这条评审意见”“这段代码评审是否有效”“评审PR反馈”“评估代码评审建议”，或在接收代码评审反馈后，需要依据客观原则对其进行批判性评估，再决定接受或拒绝时，应使用此技能。此技能仅用于评估收到的反馈，而非撰写代码评审——仅用于对反馈进行深入分析。

SKILL.md
--- frontmatter
name: critical-acceptance
description: >
  This skill should be used when the user asks to "evaluate this feedback",
  "should I accept this review comment", "is this code review valid",
  "review this PR feedback", "assess code review suggestions",
  or when code review feedback needs to be critically evaluated against
  objective principles before accepting or rejecting. Not for writing
  code reviews — only for evaluating received feedback.

Critical Acceptance Skill (비판적수용)

Critically accept user feedback based on objective principles rather than blindly following or rejecting it.

Core Principles

code
Priority 1: Objective principles (Clean Code, SOLID, Architecture)
Priority 2: Actual code behavior/intent
Priority 3: Feedback content
Priority 4: User/project preferences (reference only)

Philosophy:

  • •Feedback = subjective opinion (don't accept unconditionally)
  • •Code = primary evidence (working code is truth)
  • •All opinions are subject to verification (reviewer, user, AI included)

Execution Steps

1. Understand Feedback

  • •Who provided it? (reviewer, teammate, user)
  • •What do they suggest/criticize?
  • •Why do they think so? (evidence provided?)

2. Analyze Code

Read actual code (no guessing), search related code.

Analysis points:

  • •Does the code actually work?
  • •What is the intent?
  • •Pros/cons of current structure?

3. Evaluate with Objective Principles

See references/objective-principles.md:

  • •Clean Code: readability, simplicity, consistency
  • •SOLID: SRP, OCP, LSP, ISP, DIP
  • •Architecture: layering, separation of concerns, DRY

4. Validate Feedback

Use checklist from references/evaluation-criteria.md:

CriterionQuestion
ObjectivityBased on objective principles?
SpecificityConcrete problem and solution?
ValidityTechnically correct?
PracticalityReal benefit exists?
ConsistencyAligned with project?

5. Verify User Intent

Important: User opinions are also subject to verification

  • •If violates objective principles → point out
  • •If differs from actual code behavior → correct
  • •If inconsistent with codebase → verify

6. Make Decision & Respond

See references/examples.md for detailed examples.

ACCEPT ✅

code
Condition: Aligns with objective principles + real improvement
Action: Apply feedback

REJECT ❌

code
Condition: Violates principles OR subjective preference
Action: Keep current code + provide rationale

NEGOTIATE 🤝

code
Condition: Partially valid OR alternative exists
Action: Propose alternative and discuss

References