查找技能

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

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

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

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

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

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

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

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

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

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

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

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

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.

中文简介正在准备中。当前显示英语简介。

• Testing message delivery from the web interface to agy
• Checking terminal output against mirrored session replies
• Verifying permission requests and interruption

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

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

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

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

Review code changes with an independent agent from a different model provider. After tests pass, check a fixed diff against acceptance criteria, send blocking issues back to the implementer, and repeat until review passes.

中文简介正在准备中。当前显示英语简介。

• Get an independent review from another model provider
• Check a pull request against acceptance criteria
• Turn blocking findings into concrete fix tasks

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

Inspect imports and agent patterns in existing Python code to identify its framework and recommend an Omnigent executor, the component that runs the agent. Explain unsupported frameworks and suggest available next steps.

中文简介正在准备中。当前显示英语简介。

• Identify the framework used by existing Python agent code
• Choose an executor for Claude SDK or OpenAI Agents SDK code
• Check whether a framework has native support

Plan and review new Omnigent harness integrations, the adapters connecting agent runtimes to the platform. Compare SDK and subprocess approaches with native interface wrappers, using capability matrices and checklists for implementation and testing.

中文简介正在准备中。当前显示英语简介。

• Plan a new agent runtime integration
• Compare SDK and native integration requirements
• Review approval, streaming, and session support

Test polly's coordination of coding agents using a scripted mock language model and live command-line tools. Check startup, task dispatch, safety rules, parallel delegation, and whether real agents make appropriate orchestration decisions.

中文简介正在准备中。当前显示英语简介。

• Reproducing polly orchestration bugs
• Checking safety rules with a mock language model
• Verifying delegation and cross-review with real agents

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