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.
Document a module or public API surface (functions, classes, CLI commands, endpoints) from the code itself. Use when the user asks for API reference, to document a module, or to write usage docs for a public interface.
Review the instructions the agent will receive before you install.
Produce reference docs that match the code exactly, derived from the source, not from assumptions about what the API "probably" does.
Identify the public surface to document (a module, class, CLI command group, or set of endpoints). Then have the researcher read it carefully:
purpose: explore) to enumerate the public
entry points and report each one's real signature, parameters, defaults,
return shape, and raised errors — with file:line evidence.__all__ / export list).For each entry point:
### `<name>(<signature>)`
<one-line summary of what it does>
**Parameters**
- `<name>` (`<type>`, default `<value>`) — <meaning>
**Returns** — `<type>`: <meaning>
**Raises** — `<Error>`: <when>
**Example**
```
<minimal, runnable usage>
```
Signatures, defaults, and error types drift fastest, so route the finished
reference through the reviewer (purpose: review) to confirm every signature
and default matches the current code.
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 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.
Test Omnigent’s GitHub Copilot SDK integration on a live local server. Build test agents, run real conversations, and inspect authentication, model selection, tool connections, policy enforcement, and leftover processes to investigate integration failures.