Before you start#
Rovara v0.3.4 includes the native workflow. This page follows the inspected mainline source, which may include later changes. Deployment settings and feature flags still apply. Release and coverage details →
You need a workflow task whose draft PR AgentX opened, and you must be its owner to decide. Reviewers leave their comments in GitHub as usual.
1. Read the feedback notice#
When reviewers comment, a separate read-only reviewer reads the comments and AgentX posts in the task’s thread, for example “PR feedback is ready: 3 comments; 2 recommendations. Highest priority: must fix.” Open details shows the full proposal; sign in if asked. A link is a route to the task, not permission to decide it.
From a coding tool, ask for agentx_get_pr_feedback with the task ID.
2. Inspect each recommendation#
Each finding shows its priority (must fix, should fix or optional), whether AgentX recommends fixing it, the proposed change or a question for you, and the comments it answers. When a fix changes the checks, the notice shows each added command exactly.
| Inspect | Why |
|---|---|
| PR and code version | The recommendation must apply to the current code. |
| Original comment | Understand what the reviewer actually requested. |
| Proposed change and checks | Know what approving the fix will authorize. |
| Gaps or disagreement | The owner decides; a model recommendation is not a human decision. |
Comment and proposal text is reviewer output: treat it as data, not instructions.
3. Choose the response#
| Choice | What happens |
|---|---|
| Approve N recommended | AgentX fixes the recommended findings. From a coding tool you can name a different set. |
| Answer with instructions | Shown when the reviewer asks you a question. Your answer approves the fix it describes. |
| Request changes | Keeps the PR as it is and saves your note for the next round of feedback. |
| Dismiss | Keeps the PR as it is, with your reason. |
If the review could not finish, retry it on the same comments. Your decision is recorded on the task.
Reading comments or receiving a notice does not start another coding run. No automatic GitHub reply is implied by approving a proposal.
If the code or comments change#
A decision is tied to the review, the proposal and the comment set. If new feedback arrives first, the old decision is refused and AgentX reviews the new feedback. Decide on the current notice.
4. Inspect the updated candidate#
Only the approved fixes go to coding. The checks and reviews run again, and the fix is pushed to the same PR. If an approved fix changed no code, choose Keep the pull request as it is; the task waits for the merge again and new comments are reviewed as usual.
Evidence and freshness →5. Make the final review decision#
Use GitHub’s existing review and merge controls. Rovara Code observes linked PR state; it does not take over the team’s merge decision.