spurpower-receiving-code-review

Verify reviewer claims during a code review by running graph-based analysis tools like code_callers to check actual code structure. This enforces an evidence-based verification process, confirming factual claims regarding function usage and blast radius before responding.

Stop performative agreement when responding to code review feedback by enforcing a standardized workflow of reading, verifying, evaluating, and responding. This pattern prioritizes technical accuracy and architectural integrity over blind implementation.

Check if a function is unused before deleting it by running a graph query with code_callers and checking counts_by_kind. This provides definitive proof of the function's blast radius and usage patterns using the SPUR code graph.

This code review response method works without text search or memory by using code-explore and spur-analyst tools. These graph tools validate technical claims directly against actual code structure, ensuring factual accuracy and architectural integrity.

You can use graph analysis to evaluate the blast radius of suggested code refactoring by integrating SPUR code graph tools. This validates the architectural impact of proposed changes, ensuring technical accuracy before implementing reviewer feedback.