Documentation
README
Review code changes
Establish scope
Honor a fixed point supplied by the user. Otherwise infer a sensible comparison from the repository state, such as the default-branch merge-base. Ask only when different choices would materially change the review.
Verify that the ref resolves and inspect the diff and relevant commit messages. Report an empty or unavailable comparison instead of manufacturing findings.
Collect references
Use the repository's actual standards and the originating issue, PRD, or spec when available. Follow repository conventions for fetching tracker context. If requirements cannot be found, review the standards axis and state that spec conformance was not verified.
Evaluate two axes
This is the opening of the README. Read the full README on GitHub.