43 skills (repositories by omnigent-ai) · sorted by popularity
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.