review

To review code changes against standards and specifications, analyze the git diff to identify convention violations and missing requirements. This skill separates coding standards compliance from specification alignment, aggregating findings independently to prevent mixing concerns.

Yes, you can analyze branch changes by asking the skill to review code changes since a specified commit, branch, tag, or merge-base. It performs git diff analysis to identify implementation issues and convention violations from that reference point.

Reviewing coding standards evaluates repository convention compliance, whereas checking specification alignment verifies intended requirements are met. This skill applies a parallel analysis workflow to evaluate both axes independently before aggregating the separated findings.

Yes, this code review skill works with work-in-progress branches by assessing work-in-progress code changes against documented standards and intended specifications. It identifies implementation issues and convention violations during early branch comparisons.

Validate repository changes for missing requirements by running a git diff analysis against the intended specification. This skill discovers project issues or specifications and separately reports specification findings to highlight implementation gaps.

Use an automated code review for branch comparisons when you need to systematically identify implementation issues before merging. This skill validates repository change scenarios against documented standards and intended specifications to find convention violations.