review-feedback-followup-commits

Structure code review feedback by applying changes as distinct, logical commits rather than amending existing ones. This approach keeps the diff history clear for reviewers, coordinates with the gardening state machine, and maps review threads to specific commits for verification.

Track PR review threads by replying to each review thread with the corresponding commit SHA. This ensures reviewers can easily verify requested changes and maintains traceability between feedback and the specific fix-up commits applied.

Rebase pull request commits when a maintainer requests changes and you need to apply targeted fix-up commits. This maintains a clean, reviewable git history by organizing feedback-driven changes into distinct, logical commits rather than amending existing ones.

Yes, the review-feedback-followup-commits skill requires integration with the pr-review-thread-replies module. It also integrates with the job board and the gardening state machine to manage fix-up workflows, rebase requirements, and commit message conventions for traceability.

Use distinct follow-up commits instead of amending to keep diff history clear for reviewers. Amending obscures what changed in response to feedback, while separate commits mapped to review threads with SHAs ensure the reviewer can easily verify each requested change.

The automation depends on integration with the job board and pr-review-thread-replies modules to ensure traceability. Without these integrations, the gardening state machine cannot manage fix-up workflows, rebase requirements, or commit message conventions effectively.