receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Install with Tessl CLI
npx tessl i github:obra/superpowers --skill receiving-code-review80
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Evaluation results
100%
35%Responding to Code Review on a Data Pipeline
Handling ambiguous multi-item feedback
Identifies unclear items
100%
100%
No premature implementation
0%
100%
Does not implement clear items while unclear remain
0%
100%
Specific question on item 4
100%
100%
Specific question on item 5
100%
100%
No performative agreement
100%
100%
No gratitude expressions
0%
100%
Technical restatement of clear items
100%
100%
Without context: $0.1784 · 55s · 9 turns · 58 in / 2,572 out tokens
With context: $0.2921 · 1m 26s · 12 turns · 256 in / 4,143 out tokens
92%
16%Evaluating External Security Consultant Recommendations
External reviewer skepticism and YAGNI check
Checks actual usage
66%
80%
YAGNI determination
80%
100%
Proposes removing or deferring rather than implementing
93%
80%
Notes missing reviewer context
90%
100%
Technical reasoning in response
93%
100%
No performative agreement
100%
100%
No gratitude expressions
0%
100%
Asks clarifying question or seeks direction
70%
80%
Without context: $0.3026 · 1m 38s · 11 turns · 12 in / 4,958 out tokens
With context: $0.3481 · 1m 51s · 12 turns · 11 in / 5,639 out tokens
100%
23%Addressing Mixed-Priority Pull Request Review
Implementation prioritization and technical pushback
Security fix applied first
100%
100%
Typo fix applied
50%
100%
Complex refactor deferred or after simple fixes
100%
100%
Pushes back on config library suggestion
100%
100%
Technical reasoning for pushback
100%
100%
Escalates architectural conflict appropriately
100%
100%
No performative agreement
0%
100%
No gratitude expressions
0%
100%
Factual acknowledgment of valid fixes
70%
100%
Without context: $0.2776 · 1m 15s · 13 turns · 62 in / 3,884 out tokens
With context: $0.6013 · 2m 46s · 21 turns · 314 in / 8,859 out tokens
- Evaluated
- Agent
- Claude Code
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.