Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From cc-useful
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.
npx claudepluginhub jhleee/cc-useful --plugin cc-usefulHow this skill is triggered — by the user, by Claude, or both
Slash command
/cc-useful:critical-acceptanceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Critically accept user feedback based on **objective principles** rather than blindly following or rejecting it.
Enforces verification-first code review: evaluate suggestions rigorously before implementing, push back when feedback is incorrect or lacks context.
Evaluates code review feedback with technical rigor before implementing. Verifies suggestions against codebase reality, handles unclear items, and pushes back with reasoned arguments when appropriate.
Evaluates code review feedback with verification before implementing. Checks if issues are real, fixes are correct, and changes don't break other things. Includes patterns for reasoned pushback.
Share bugs, ideas, or general feedback.
Critically accept user feedback based on objective principles rather than blindly following or rejecting it.
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:
Read actual code (no guessing), search related code.
Analysis points:
See references/objective-principles.md:
Use checklist from references/evaluation-criteria.md:
| Criterion | Question |
|---|---|
| Objectivity | Based on objective principles? |
| Specificity | Concrete problem and solution? |
| Validity | Technically correct? |
| Practicality | Real benefit exists? |
| Consistency | Aligned with project? |
Important: User opinions are also subject to verification
See references/examples.md for detailed examples.
ACCEPT ✅
Condition: Aligns with objective principles + real improvement
Action: Apply feedback
REJECT ❌
Condition: Violates principles OR subjective preference
Action: Keep current code + provide rationale
NEGOTIATE 🤝
Condition: Partially valid OR alternative exists
Action: Propose alternative and discuss