code-review-and-commit

Splitting changes into conventional commits involves inspecting unstaged and staged diffs to group related modifications. This process builds an atomic commit plan, ensuring each commit represents a single logical change for better maintainability.

Preparing a safe Git workflow requires inspecting local working tree changes for correctness and convention alignment. It outputs a structured commit plan with an approval gate before executing git add or git commit, ensuring auditable history.

You can enforce project conventions by inspecting unstaged and staged changes for alignment. The review process proposes targeted fixes to maintain code quality and ensures modifications adhere to established repository standards before committing.

Yes, the code review process provides an explicit approval gate before performing git add and git commit. This ensures safe, auditable history by requiring user validation of the structured commit plan before any version control actions execute.

You should not use automated code review when dealing with changes that require subjective architectural decisions beyond convention alignment. It is designed for deterministic inspection of local diffs and generating safe commit plans, not deep semantic logic validation.