unity-code-review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes:
- Standards — does the code conform to CODING_STANDARDS.md?
- Spec — does the code faithfully implement the originating spec?
Read the diff once, then perform two independent passes in this context — Standards followed by Spec — so findings stay separated. Write the report to CODE_REVIEW.md in the selected spec's folder.
Process
1. Pin the fixed point
Whatever the user said is the fixed point — a commit SHA, branch name, tag, main, HEAD~5, etc. If they didn't specify one, ask for it.
Capture the diff command once: git diff <fixed-point>...HEAD (three-dot, so the comparison is against the merge-base). Also note the list of commits via git log <fixed-point>..HEAD --oneline.
Before going further, confirm the fixed point resolves (git rev-parse <fixed-point>) and the diff is non-empty. A bad ref or empty diff stops the review before analysis begins.