本文へ移動
cccskills
無料GitHub で公開

otto-review-remediation

Handle trusted reviewers' change requests on Otto PRs.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.2 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Review-remediation mode

Shared by Otto agents that remediate their own PRs (Resolve's review_pr mode). When review_pr is present, this procedure takes precedence over the agent's reproduction and candidate-PR discovery instructions.

Handoff contract. Finish with mode: "review_remediation", reviewed_pr_url and pr_url set to review_pr, the scanner's review fingerprint, the handled review ids, and the final pushed head (step 8).

  1. Confirm the working checkout is the named PR's current head and remains on its existing head repository and branch. Never create a replacement PR, rebase, reset, rewrite history, force-push, or push to the base branch.
  2. Read the PR body, diff, all reviews, inline comments, unresolved threads, current checks, Polly and OCR feedback, and recent failed job logs. Treat the latest decisive review from each human reviewer as authoritative.
  3. Address every current substantive CHANGES_REQUESTED item from trusted human reviewers. Use the agent's investigation procedure (Resolve: resolve-investigate) for ambiguous intent or product judgment and put a supported proposal on this PR. If authoritative requests conflict, required inputs are missing, or a request is unsafe or outside authorization, explain the blocker and continue independent authorized work. Do not dismiss or silently override human reviews.
  4. Complete the shared impact assessment for the full PR, including your remediation edits, and run its focused checks. Commit as the agent's bot identity (Resolve: omni-resolve-agent[bot]), and push directly to the existing PR branch using the workflow-provided push command. For a contributor fork, use only that fixed-target command; never inspect or export its credential source.
  5. Continue through CI/mergeability (Resolve: Step 4.2) and the shared otto-pr-review-loop skill (Resolve: Step 4.3) until current CI is green and both Polly and OCR have completed on the current head with no actionable findings. Diagnose PR-caused failures, rerun clearly transient failures, push conservative fixes, and rerun both reviewers after every push. Run the review loop's live gate before a successful handoff.
  6. Reply to addressed review threads with the commit and validation evidence, resolve a thread only when fully addressed, and request re-review from the humans whose change requests were handled. Never approve, dismiss a human review, or merge.
  7. Skip the agent's other entry phases (Resolve: reproduction handoff recovery, fail-before proof, recording generation, candidate-fix discovery, new-PR creation, UI-preview setup) unless already required by the PR. The trusted workflow publishes idempotent remediation start and completion comments on both the GitHub PR and its attached Linear issue; preserve the attached issue in bug_url so those comments stay linked.
  8. Finish with the normal handoff using mode: "review_remediation". Set bug_url to an attached bug when one is clear, otherwise ""; set reviewed_pr_url and pr_url to review_pr; include the review fingerprint, handled review ids, and final pushed head.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Spin up a live local Omnigent server + runner and exercise the native Antigravity (agy) TUI harness (antigravity-native) end-to-end — launch the real `agy` CLI via `omnigent antigravity`, drive turns through the web UI, smoke-test, and bug-bash. Load when developing, testing, or debugging the antigravity-native harness (omnigent/inner/antigravity_native_executor.py, omnigent/antigravity_native.py, antigravity_native_bridge.py, antigravity_native_rpc.py, antigravity_native_reader.py, antigravity_native_launch.py) or its agy launch / RPC mirror / tmux delivery / OAuth / MCP-relay behavior. NOT the in-process `antigravity` Gemini SDK harness.

日本語の概要は準備中です。原文の説明を表示しています。

omnigent-ai/omnigent1.1万2026年10月17日 更新

Spin up a live local Omnigent server and exercise the Antigravity (Gemini) SDK harness end-to-end — build antigravity agents, run real turns, smoke-test, and bug-bash. Load when developing, testing, or debugging the antigravity harness (omnigent/inner/antigravity_executor.py, antigravity_harness.py, omnigent/onboarding/antigravity_auth.py) or its auth / model / tool-bridge behavior.

日本語の概要は準備中です。原文の説明を表示しています。

omnigent-ai/omnigent1.1万2026年10月17日 更新

api-docs

無料

Document a module or public API surface (functions, classes, CLI commands, endpoints) from the code itself. Use when the user asks for API reference, to document a module, or to write usage docs for a public interface.

日本語の概要は準備中です。原文の説明を表示しています。

omnigent-ai/omnigent1.1万2026年10月17日 更新

Patterns and templates for generating valid Omnigent agent directories. Load when ready to create files.

日本語の概要は準備中です。原文の説明を表示しています。

omnigent-ai/omnigent1.1万2026年10月17日 更新

changelog

無料

Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.

日本語の概要は準備中です。原文の説明を表示しています。

omnigent-ai/omnigent1.1万2026年10月17日 更新

Verify the Omnigent CLI's setup/onboarding flow, terminal UI/UX, and critical user journeys in a completely isolated, reproducible loop. Drives the real `omnigent` binary through a PTY (pexpect) inside a throwaway OMNIGENT_CONFIG_HOME / OMNIGENT_DATA_DIR sandbox that never touches the user's real ~/.omnigent, captures ANSI-stripped frames for UX inspection, and proves a change is verifiable via a before→fix→after baseline diff. Load when developing or reviewing a CLI setup/onboarding/REPL/picker change (omnigent/cli.py, omnigent/onboarding/*, omnigent/repl/*, scripts/install_oss.sh), reproducing a cold-start/first-run UX bug, or confirming a fix actually lands. Several agents can run it concurrently on separate worktrees.

日本語の概要は準備中です。原文の説明を表示しています。

omnigent-ai/omnigent1.1万2026年10月17日 更新

omnigent-ai のスキルをすべて見る

このスキルの問題を報告する