Fine-tune pull requests inside GitHub.

Your team already reviews code in GitHub. Leave a comment on an agent's pull request and the fix arrives as a follow-up commit on the same branch.

Comment-to-commit Same PR branch

PR Comment "fix the padding"

Isolated RunAgent applies fix

New CommitAdded to branch

Review continues in GitHub

A review comment starts the isolated run, and the resulting commit lands on the same PR branch.

Line-level context

A line comment carries its file and line, so the agent knows exactly what to change.

Image-aware comments

Paste a screenshot into the comment. The agent reads it for visual bugs and UI polish.

Intentional triggers

Choose which comments or prefixes start an agent run, so casual discussion costs nothing.

Single-branch history

Follow-up commits land on the existing PR branch, so the whole review reads in one place.

One comment, one commit.

On public propr #1613, a maintainer asks for streamed Docker startup progress. ProPR answers with the commit and the checks it ran.

A recent human follow-up request on public ProPR pull request 1613. — Comment to commit on public propr #1613.

ProPR replying with the follow-up commit and passing verification. — Comment to commit on public propr #1613.

Every PR action runs from a comment.

Fixes, review loops, branch updates and rollbacks all start from the pull request conversation.

A review scored 6 with two issues, then the /fix run that applies finding F1 and suggestion S2

Apply review findings

/fix applies the merge blockers from /review, and /fix all adds the suggestions. Trim the review's copyable /fix F20 S3 line to apply only the ones you keep.

One pull request’s runs: review scored 5, a fix, review scored 7, and the Ultrafix cycle in progress

Ultrafix loop

/ultrafix runs review and fix cycles toward your target score, within your cycle limit. Watch one loop on a real PR.

A /merge run on the pull request: merge main into the branch, resolve the conflict in CheckoutSummary.tsx, run the checkout tests

Branch updates

/merge brings a stale branch up to date with its base and resolves the conflicts.

The undo link’s preview: the merge commit becomes the new head and the follow-up commit after it is removed

One-click revert

Every follow-up commit comes with an undo link in its completion comment.

Choose the right model for the job.

Pick separate agents and models for planning, implementation and refinement, all in one workflow.

See supported agents →