cmd-workflow-pr-fix

Automate PR review comment resolution by categorizing feedback into blocking issues, questions, suggestions, and nitpicks, then implementing code fixes and replying inline to reviewers. It uses GitHub CLI commands to fetch PR details and apply changes scoped only to the files modified in the PR.

Replying inline to code review threads is handled by posting concise explanations directly to the specific reviewer comments. The workflow references the atomic commits where fixes were applied, ensuring clear traceability between the requested change and the implementation.

Categorize pull request feedback by parsing reviewer comments into distinct groups such as blocking issues, questions, suggestions, and nitpicks. This classification determines the priority of fixes and ensures only relevant code changes are implemented within the PR scope.

Yes, the PR fix workflow runs a verification process that includes tests, linting, and CI checks before pushing. It creates atomic commits for the fixes and ensures all changes are validated and confined to the PR scope prior to a push or merge.

Yes, you can use GitHub CLI commands like 'gh pr view', 'gh pr diff', and 'gh api' to manage and fix pull request review suggestions. The workflow retrieves PR details and review feedback directly via the CLI to implement and verify the required code changes.

You should not automate applying fixes when the reviewer feedback requires architectural changes outside the current PR scope or open-ended design discussions. The workflow is designed for scoped code changes, linting verification, and structured atomic commits, not for resolving broad conceptual debates.