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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 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.
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.
Run concurrent Omnigent conversations with real hosts and runners while replacing the LLM with a zero-latency mock. Read the generated report to explain response-time distributions, throughput, and failures, helping assess Omnigent's own processing overhead.
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.
Move an open pull request, a proposed code change, toward maintainer review by coordinating automated checks, two independent reviews, preview preparation, and live validation instructions, while tracking fixes and unresolved work.
Prepare a bug-fixing run by recovering reproduction details and tests, checking the workspace, and finding existing fixes. Select the appropriate workflow for a reproduction session, CI run, bug ticket, or requested PR changes.
Commit a validated bug fix and follow the selected publication path: keep it local, prepare it for a CI publisher, or open a pull request. Organize the description, regression test evidence, and handoff details for review.
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.
Have Claude and GPT critique each other's answers, revise their positions, and work toward a combined response. Choose the number of rounds and see what changed, where they agree, and which disagreements remain.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)