Guide pull request checks for merge readiness, automated checks, and live previews. It points agents to shared instructions at the relevant stage and identifies facts to include when handing work over to maintainers.
PR mergeability, CI, and live preview.
Review the instructions the agent will receive before you install.
Read each resource when the agent's PR-driving procedure reaches its substep:
| Substep | Resource |
|---|---|
| 4.2, current CI and mergeability | ci.md |
| 4.1, preview after CI and both reviews are clean | preview.md |
Use read_skill_file with this skill name and the relative filename, or read
relative to the directory supplied by the native Skill tool.
Substep numbers follow Resolve's resolve-drive-pr: 4.3 is the shared
otto-pr-review-loop, and 4.4/4.5 are the agent's own live-validation and
maintainer-handoff steps. "Fix" and "bug" mean the PR's change. The review path
and fork takeovers apply only to agents that review other authors' PRs. Handoff
fields named here (ci_status, ui_preview, validation_surface,
files_changed) are Resolve's; record the same facts in your agent's handoff.
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.