openclaw-review

To review code changes on a staging branch, you can capture a snapshot of the work, manually validate the code diff against a checklist, and then make a decision to merge or reject the task. This ensures code quality before integration.

Managing task state after a code review involves updating the task status in the state engine to either "completed" for approved changes or "rejected" for unapproved work, ensuring the system tracks the outcome of the diff validation.

Capturing a snapshot of specialist code changes requires using git branch operations to isolate the submitted work, allowing an L2 agent to manually review the differences and verify them against project standards before merging.

Yes, the code review workflow requires integration with git for branch operations to manage staging branches, and it also connects to a state engine to update task statuses accurately based on review outcomes.

You should reject a specialist task instead of merging when the manual diff validation identifies failures in meeting project requirements, triggering a rejected status in the state engine to provide specific feedback for revisions.

Yes, you can use this to orchestrate an L2 diff review for L3 specialist changes, managing the workflow from capturing code snapshots on staging branches to making the final decision to merge or reject the submitted work.