groove-work-review

Evaluate code changes against acceptance criteria by analyzing git diffs to identify specific gaps, categorizing findings into 'Fix Now', 'Needs Spec', or 'Create Issues', and appending review notes directly to the task body to determine if work should be accepted or reworked.

Automating code review and capturing lessons learned involves assessing implemented work artifacts against project plans, making an accept or rework decision, and recording insights for the compound engineering loop to improve future development iterations.

Categorize code review findings by grouping identified gaps into three specific buckets: 'Fix Now' for immediate corrections, 'Needs Spec' for unclear requirements, and 'Create Issues' to generate new tasks for future rework actions.

Yes, you can use artifact evaluation to clearly determine whether to accept implemented work or require rework by verifying deliverables against defined plans and acceptance criteria, providing a clear rationale for the decision.

No, effective code review requires existing project plans and defined acceptance criteria to compare against. Without these baselines, the evaluation cannot accurately identify specific gaps or make a reliable accept or rework decision for the deliverables.

You should avoid automated git diff evaluation when project plans and acceptance criteria are undefined, or when evaluating complex architectural changes that require manual contextual review beyond identifying specific gaps and generating rework tasks.