Use Autohand Code to read reviewer comments, map each point to code, patch only the needed files, and rerun focused checks.
Turn review feedback into a clean follow-up patch
Quality Quality and review Review Review
autohand -p "Address these PR review comments with a focused patch and rerun the relevant checks"
A small follow-up diff that resolves comments and explains remaining tradeoffs.
Address PR review comments with Autohand Code is a review follow-up workflow that maps reviewer feedback to code, resolves comments with a narrow diff, and records the checks that prove the patch. ### At a glance | Question | Answer | | --- | --- | | Best for | requested changes, unresolved review threads, small post-review corrections, and comments that mention exact files or behavior | | Primary inputs | Review comments, requested changes, or copied PR thread text; The current branch diff and base branch context; Checks that reviewers expect before re-requesting review | | Autohand Code returns | A small follow-up diff that resolves comments and explains remaining tradeoffs. | | Avoid when | the feedback changes product direction or requires a new design decision before implementation | ### How Autohand Code handles this workflow 1. Groups review comments by code area and distinguishes actionable requests from discussion. 2. Edits only the files needed to resolve the comments. 3. Keeps reviewer intent visible when a comment has several possible fixes. 4. Reruns focused checks and summarizes any comment that still needs human judgment. ### Best inputs - Review comments, requested changes, or copied PR thread text - The current branch diff and base branch context - Checks that reviewers expect before re-requesting review ### Strong prompt autohand -p "Address these PR review comments with a focused patch and rerun the relevant checks" ### Autohand Code CLI options - Pipe review text or paste comments into `autohand -p "Address these PR review comments with a focused patch and rerun the relevant checks"`. - Use `/review` after the patch to catch regressions before handing the PR back. - Use `--patch` when you want a proposed diff for inspection before applying changes. ### Review before accepting The final note should map each comment to the changed file, validation command, or remaining decision. ### Source and validation signals Autohand AI maintains this workflow as first-party product guidance for Autohand Code. Use the [Autohand CLI Playbook](https://github.com/autohandai/code-cli/blob/main/docs/AUTOHAND_PLAYBOOK.md), [CLI reference](/docs/working-with-autohand-code/cli-reference.html), and [configuration reference](https://github.com/autohandai/code-cli/blob/main/docs/config-reference.md) when choosing between interactive mode, command mode, auto-mode, feature-enabled /goal, /settings, skills, MCP, and permission settings. The related resources below link to product docs and tutorials for the workflow, and the final answer should name repository-specific files, commands, outputs, or docs that a reviewer can verify. ### Frequently asked questions ### What is Address PR review comments with Autohand Code? Address PR review comments with Autohand Code is a review follow-up workflow that maps reviewer feedback to code, resolves comments with a narrow diff, and records the checks that prove the patch. ### When should a team use Address PR review comments? Use it after a PR has concrete reviewer feedback and the best next step is a small correction pass. ### What evidence should reviewers check for Address PR review comments? The final note should map each comment to the changed file, validation command, or remaining decision.
Tutorial Run Code Review Use Autohand Code to inspect a diff before sending it back. /docs/tutorials/run-code-review.html Guide Git Flow Automation Keep branch, review, and validation steps in a clean flow. /docs/guides/git-flow-automation.html Reference Plan Mode Separate reviewer intent, implementation steps, and validation before editing. /docs/working-with-autohand-code/plan-mode.html