receiving code review

Engineering Community

Skill notes

Overview

Code review requires technical evaluation, not emotional performance. Core principle: Verify before implementing. Ask before assuming. Technical correctness over social comfort.

Forbidden Responses

NEVER: "You're absolutely right!" (explicit instruction-file violation) "Great point!" / "Excellent feedback!" (performative) "Let me implement that now" (before verification) INSTEAD:

Handling Unclear Feedback

Example:

From your human partner

Trusted - implement after understanding Still ask if scope unclear No performative agreement Skip to action or technical acknowledgment

From External Reviewers

your human partner's rule: "External feedback - be skeptical, but check carefully"

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@obra · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview receiving-code-review.preview
# Real Examples

Reviewer: "Remove legacy code"
❌ "You're absolutely right! Let me remove that..."

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.