runtime-code-review

Runtime Code Review

1. Default review scope to uncommitted changes. Expand to adjacent files only when needed to understand behavior.
2. Run the execution-risk-check workflow before any runtime command.
3. Infer the nearest local test or script when confidence is high.
4. Ask for a command when the runtime target is ambiguous.
5. Use mcp-debugger to validate assumptions around changed code:
   • break on the changed area
   • inspect variables and control flow
   • confirm unexpected behavior before reporting it
6. Findings should prioritize concrete bugs, regressions, and missing tests over style.