Address trusted human reviewers’ change requests on an existing Otto pull request. It guides fixes on the same branch, verification, replies with supporting evidence, and requests for another review before handing over the results.
Handle trusted reviewers' change requests on Otto PRs.
Review the instructions the agent will receive before you install.
Shared by Otto agents that remediate their own PRs (Resolve's review_pr mode).
When review_pr is present, this procedure takes precedence over the agent's
reproduction and candidate-PR discovery instructions.
Handoff contract. Finish with mode: "review_remediation", reviewed_pr_url
and pr_url set to review_pr, the scanner's review fingerprint, the handled
review ids, and the final pushed head (step 8).
CHANGES_REQUESTED item from trusted human
reviewers. Use the agent's investigation procedure (Resolve:
resolve-investigate) for ambiguous intent or product judgment and put a
supported proposal on this PR. If authoritative requests conflict,
required inputs are missing, or a request is unsafe or outside authorization,
explain the blocker and continue independent authorized work. Do not dismiss
or silently override human reviews.omni-resolve-agent[bot]), and push directly to the
existing PR branch using the workflow-provided push command. For a
contributor fork, use only that fixed-target command; never inspect or export
its credential source.otto-pr-review-loop skill (Resolve: Step 4.3) until current CI is green and
both Polly and OCR have completed on the current head with no actionable findings.
Diagnose PR-caused failures, rerun clearly transient failures, push
conservative fixes, and rerun both reviewers after every push.
Run the review loop's live gate before a successful handoff.bug_url so those comments stay linked.mode: "review_remediation". Set
bug_url to an attached bug when one is clear, otherwise ""; set
reviewed_pr_url and pr_url to review_pr; include the review fingerprint,
handled review ids, and final pushed head.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Test Omnigent’s native Antigravity integration with a live local server and the real agy CLI. Verify messages traveling between the web interface and terminal, mirrored replies, permission requests, interruption, session resumption, and process cleanup.
Test Omnigent’s Antigravity SDK integration against a live local server. Build test agents and run real conversations to check Gemini authentication, model selection, tool connections, and failures across the full execution path.
Create reference documentation directly from source code for public functions, classes, command-line commands, and endpoints. Organize parameters, defaults, return values, errors, and runnable examples, then check that the documentation matches the implementation.
Create an Omnigent agent directory using validated templates for configuration and instructions. Choose how the agent runs, then add web search, shell access, external tool connections, or subagents only when the task requires them.
Turn a selected range of commits or merged pull requests into release notes grouped by change type. Describe user-visible effects, link to supporting changes, and highlight breaking changes so readers can assess an upgrade.
Test Omnigent’s setup, help, and terminal interactions by driving the real CLI in an isolated environment. Capture rendered screens and compare checks before and after a change to establish whether a reported interface problem was fixed.