Turn PR feedback into a follow-up commit.

Write a comment on the PR and get the next commit back. This is the PR fine-tuning loop; GitHub comment control covers every other comment action.

Describe

Run isolated

Review in GitHub

You start with: A ProPR pull request ready for review
You use: PR comments · /review · /fix
Takes: One comment per change

Open the generated PR

Open the pull request ProPR created and review the summary, commits, changed files, and checks. Your next instruction goes in the PR conversation or on a diff line.

Leave feedback

Post a comment that states the change you want. Plain PR comments and line-level review comments both start follow-up work.

@rinaldscommented on this pull request

@propr Please extract the database connection string into a separate utility file and add a retry block for timeouts.

That comment becomes a focused follow-up task with the current PR context. For line-specific feedback, leave the note on the diff line and ProPR gets the file and line too.

Choose the command shape

Write plain text for a normal refinement, /review for a read-only AI critique, /fix to apply a review's merge blockers or the F#/S# records you name, and /switch to route the next pass to another agent or model. See every command in GitHub comment control.

Please tighten the error handling in the auth callback.
Please extract the database connection string into a separate utility file.
/review Focus on security, migrations, and test coverage.
/switch astra

ProPR starts the follow-up

ProPR turns the comment into a follow-up task with the PR conversation, diff, and line context, and runs the agent in an isolated workspace. A /fix comment applies the pending merge blockers from /review instead; /fix all adds the optional suggestions.

A follow-up run on the pull request: read the PR comment about the phone layout, move the summary below the form, run the checkout tests

Expected result

ProPR commits the change to the same PR branch, so reviewers see one more normal commit and the discussion stays in one thread. ProPR replies with the outcome and links to the task, the commit, and a revert. Looks good? Merge it. Went the wrong way? Revert it.

@propr-dev[bot]bot

✅ Follow-up complete. Extracted the database connection string into a utility file and added a 3-retry backoff for timeouts.

🔗 Commit a1b2c3d · ⏱️ Duration 42s · 🔄 Revert this change

The undo link’s preview: the merge commit becomes the new head and the follow-up commit after it is removed — Revert previews exactly which commit leaves the branch.

What you get

Each comment becomes one more commit on the same PR branch, with a reply that links the task, the commit and an undo.

PR fine-tuning → All playbooks