스킬 찾기

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

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

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

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

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

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

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

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

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.

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

• Writing reference docs for a public module
• Documenting command-line arguments and defaults
• Adding minimal usage examples for an API

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

Review code or changes for exposed secrets, injection risks, weak encryption, and missing permission checks. Produce a structured report with severity, location, recommendations, and confidence, with a separate reviewer checking findings for false positives.

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

• Reviewing a module for security issues
• Checking changes for exposed secrets
• Preparing a vulnerability report with evidence

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.

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

• Creating a minimal Omnigent agent
• Configuring an agent with web search
• Adding shell access or MCP tool connections

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

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

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.

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

• Stress-testing a proposal from two perspectives
• Finding weaknesses in competing answers
• Combining agreement while preserving unresolved differences

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 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.

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

• Reproducing a first-run setup problem
• Inspecting menus in a narrow terminal
• Checking help text and command visibility

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

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

Build and run Omnigent’s server and Postgres together with Docker Compose on a laptop or existing Docker host. Use the supplied configuration and troubleshooting guidance to rebuild images, investigate startup problems, or adapt deployment to another platform.

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

• Running Omnigent locally with Postgres
• Starting the stack on an existing VPS or EC2 host
• Investigating startup and web interface problems