Follow-up fixes
A normal PR comment or a line-level review comment becomes a focused follow-up task. File and line context stay attached when the comment came from code review.
ProPR keeps PR iteration inside GitHub. A normal comment requests another implementation pass. A review command asks an AI agent to critique the pull request. Once that review lands, /fix applies the AI review suggestions you keep. Branch cleanup and recovery happen from the same PR thread.

ProPR applies the request on the same branch

A normal PR comment or a line-level review comment becomes a focused follow-up task. File and line context stay attached when the comment came from code review.
/review posts read-only AI review comments. /fix is the follow-up that applies the unprocessed suggestions you leave in place.
/ultrafix bundles review and fix passes until the target score is reached, the configured cycle limit is hit, or a person stops it.
Update a stale PR branch from the thread; merge conflicts move through the same isolated task path.
Pull screenshots from GitHub issues or comments into follow-up changes for UI feedback and visual bugs.
ProPR posts the outcome back to GitHub with task links, commit details, and recovery paths when available.
GitHub comments express intent. Plain comments request routine follow-up work; slash commands handle specific control actions and post the result back on the same pull request.
/reviewRun a read-only review against the current PR. ProPR posts tagged AI review comments with the findings and score while leaving code unchanged. Name one or several models — /review <model-a> <model-b> — to get independent reviews side by side.
/fixUse after /review. ProPR gathers unprocessed AI review comments, applies the suggestions in one follow-up pass, and marks them as handled. For ordinary change requests, use a plain PR comment instead.
/ultrafixStart with /review unless review comments are already pending, then alternate review and fix until the loop hits the target score, the configured max cycles, or a manual stop.
/mergeMerge the base branch into the PR branch from the thread. If conflicts appear, ProPR attempts an automatic resolution in an isolated task and reports the result on the PR.
Plain commentDescribe the observed problem and expected result. ProPR turns the comment into another focused task on the same pull-request branch.
/switchUpdate the model label for future follow-ups and optionally include instructions in the same comment.
A concrete change request gets another commit on the same PR; stale branches and conflicts move through the same GitHub conversation when the branch needs to be updated safely. For repeated cleanup, Ultrafix chains review and fix cycles inside the broader GitHub PR loop.