omnigent

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking CI status and merge readiness
• Preparing a preview after reviews pass
• Organizing facts for a maintainer handoff

Prepare a structured JSON handoff for feature work, bringing together requirements, design decisions, key user journeys, tests, demo recordings, and pull request status. Clearly distinguish completed work from missing validation, publication steps, and other remaining tasks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing a final handoff for feature development
• Linking key user journeys to tests and demo recordings
• Reporting unpublished work and remaining validation

Choose a feature design using the relevant code, requirements, and existing conventions. Record the chosen approach, alternatives, risks, and coverage of key user journeys, and identify decisions that need human input before implementation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choose an implementation approach before coding
• Document alternatives and reasons for rejecting them
• Check coverage of key user journeys

Commit a completed feature and prepare a pull request describing its design, tests, and demos. Follow the selected publication mode, and for direct publication, work through automated checks and review feedback before requesting maintainer review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Commit a completed feature using repository conventions
• Prepare a pull request with tests and demos
• Address automated checks and review feedback after publication

Implement a feature from its design and connect each covered user journey, a sequence of user actions, to a meaningful test. Run focused checks and assess the full change for effects on existing behavior.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implement a feature from an agreed design
• Connect key user journeys to tests of new behavior
• Assess effects on existing behavior before preparing a demo

Assess the full code change for effects on callers, configuration, and related behavior. Organize focused tests, execution evidence, and unverified areas to support decisions about whether a fix or pull request is ready.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check effects on callers of shared code
• Organize test evidence before approving a pull request
• Report unverified areas before handing off a fix

Record product demos that show real user actions and responses for each covered user journey. Add timed captions, inspect the finished clips, and include them in pull requests, with manual test instructions when recording is blocked.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Showing a feature's real user flow in a pull request
• Recording CLI or API behavior in a terminal
• Adding action and result captions to demo clips

Turn a feature ticket into clear requirements and critical user journeys, describing who does what and the expected result. Check the scope before design begins, and propose smaller dependent tickets when the work exceeds one reviewable change.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning a feature ticket into user-facing requirements
• Mapping critical journeys across interfaces
• Checking scope before design and implementation

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Addressing human reviewers’ requested changes
• Fixing and validating changes on the existing PR branch
• Replying to review threads with commits and test evidence

Prepare feature work by reading a Linear ticket and its context, checking development tools, and looking for existing implementation or pull requests. Route requested PR changes to a separate review workflow before development proceeds.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review a feature ticket before starting development
• Check for existing implementation or an active PR
• Confirm development tools and branch setup

Run Polly AI Review and Open Code Review repeatedly on a pull request. Track each finding, fix relevant issues, document justified dismissals, and verify that review evidence and recorded decisions cover the latest commit.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Resolving findings from two automated PR reviewers
• Reviewing each new commit after fixes
• Recording evidence for dismissed or duplicate findings

Draft or refresh Omnigent release notes for a specific version and commit range. Review merged pull requests, verify user-facing highlights and contributor credits, and deliver unpublished notes alongside a complete changelog preview.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Draft release notes before a version tag exists
• Refresh a reviewed draft while preserving editorial changes
• Review breaking changes and upgrade guidance

Investigate a reported bug before choosing a fix. Trace the actual failure, test competing explanations, and examine design history so the proposed change preserves intended behavior and clearly separates verified findings from unresolved assumptions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reconstructing the conditions of a reported bug
• Distinguishing a symptom from its underlying cause
• Checking intended behavior in tests and history

Test Omnigent’s native Pi integration using the real terminal interface and a local server. Verify messages sent through the web or API, recorded replies, interruption, session resumption, authentication, and model settings to investigate integration problems.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking message delivery from the web or API to Pi
• Verifying replies appear in the server transcript
• Testing interruption, resumption, and tool policies

Investigate a bug's root cause, implement a focused repair, and verify the same behavior before and after the change. Select lasting regression tests, preserve reproduction evidence, and record the corrected user journey when possible.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating and fixing a bug without an existing candidate PR
• Proving a repair with failing-then-passing tests
• Consolidating regression checks into existing tests

Research questions on the web and produce a report with source links. Read full pages, check important claims against independent sources, and clearly distinguish supported findings from uncertain evidence or disagreements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Research a question that requires current information
• Cross-check important claims across independent sources
• Compare conflicting accounts and explain uncertainty

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Test authentication and real Gemini responses
• Verify tool connections and sub-agent delegation
• Investigate model selection failures

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking Copilot authentication with a real conversation
• Testing model selection and tool connections
• Verifying sub-agent dispatch and policy enforcement

Audit recovered bug reproduction tests before writing a fix or reviewing a pull request. Check that assertions reflect intended behavior, establish a valid failure on unfixed code, and verify the same test passes after the fix.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking recovered reproduction tests before fixing a bug
• Validating test evidence for a pull request
• Rewriting weak assertions around actual behavior

Review an existing bug-fix pull request using validated reproduction tests and the complete code diff. Assess root-cause coverage, scope, and regressions, then document behavioral evidence and follow the workflow's branch and approval rules.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Independently verifying an existing bug-fix pull request
• Checking a complete diff for scope and root-cause coverage
• Recording the user journey on the proposed fix

Verify Omnigent behavior through real user actions in an isolated environment. Use a feature map to cover relevant web, terminal, and CLI entry points, preserving recordings and other evidence for bug reproductions and fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reproducing a user-facing Omnigent bug
• Comparing behavior before and after a fix
• Checking coverage across web, terminal, and CLI entry points

Test Omnigent’s Cursor SDK integration against a live local server. Build test agents, run real conversations, and check authentication, model selection, and tool connections while investigating empty responses or bridge processes left after shutdown.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Test Cursor authentication and real responses
• Verify file operations and sub-agent delegation
• Investigate invalid models and empty output

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Write release notes covering changes since the last tag
• Summarize pull requests merged during a selected period
• Highlight breaking changes before an upgrade

Look up how to configure and organize Omnigent agents. Use examples to choose an executor, the agent's runtime, arrange instructions and skills, add local tools or external services, and define specialized child agents.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check agent directory layout and config.yaml settings
• Choose an executor and harness
• Add skills, custom tools, or MCP services