What problem does it solve? After receiving a code review, an agent must decide which findings are technically valid, implement accepted fixes, and document the reasoning for every accept or reject decision. This Skill enforces a rigorous, anti-sycophancy evaluation protocol so responses are grounded in the actual codebase rather than the reviewer's framing. ## Core Features & Use Cases - Finding evaluation protocol: Parses numbered findings (F, W, T, R, S, and legacy -L variants) and applies hard-gate rules requiring verification against the actual code before acceptance. - Structured change summary artifact: Produces a coder_change-summary markdown artifact with YAML frontmatter, per-finding ACCEPT/REJECT/PARTIAL dispositions, rationale, and action taken, saved into the run directory. - Diff audit and commit integration: Verifies implemented fixes against the diff before writing the response and commits accepted changes via the create-commit skill. - Use Case: A reviewer flags that a constant should move to a config module; the agent reads the destination file's stated doctrine, accepts or rejects with cited evidence, implements accepted fixes, and saves a dispositioned change summary. ## Quick Start Ask the agent to respond to the most recent code review for the current ticket, or pass a path to a specific review file to disposition its findings.
