Open the generated PR
Open the pull request ProPR created and review the summary, commits, changed files, checks, and completion details. The next instruction belongs in the PR conversation or in a line-level review comment.
GitHub feedback becomes the next commit through the PR fine-tuning loop, and GitHub comment control covers the broader comment-driven actions.
Open the pull request ProPR created and review the summary, commits, changed files, checks, and completion details. The next instruction belongs in the PR conversation or in a line-level review comment.
Post a concrete GitHub comment that states the change you want. Normal PR comments and line-level review comments are the primary way to request follow-up implementation work.
That exact comment asks ProPR to create a focused follow-up task from the current PR context. For line-specific feedback, leave the same kind of natural-language note on the relevant diff line so GitHub supplies the file and line context.
Use plain follow-up text for a normal refinement, /review for a read-only AI critique, /fix only after /review has posted AI review suggestions you want applied, and model routing when this pass needs a different agent or model. The broader command surface is covered 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 claude-code sonnetProPR turns the submitted comment into a follow-up task, attaches the PR conversation, diff, and line context where available, and runs the selected agent in the same isolated workflow described by PR fine-tuning. If the comment is /fix, ProPR instead gathers the unprocessed AI review suggestions previously posted by /review and applies those selected findings.
ProPR commits the follow-up change back to the same PR branch, so reviewers see another normal commit on the existing pull request. The full discussion stays in one thread. When the task finishes, ProPR replies in GitHub with the outcome, links to the task or commit, and any available recovery path. If it looks good, merge it; if the agent went the wrong way, back it out from the linked revert.
โ Follow-up complete. Extracted the database connection string into a utility file and added a 3-retry backoff for timeouts.
@propr Please extract the database connection string into a separate utility file and add a retry block for timeouts.