Agent Skills
› omnigent-ai/omnigent
› otto-review-remediation
otto-review-remediation
GitHub自动处理可信评审者对PR的修改请求,通过修复代码、解决CI失败及验证闭环,确保PR在合并前满足所有审查要求。
Trigger Scenarios
收到PR评审中的CHANGES_REQUESTED反馈
需要修复PR以通过CI和审查
Install
npx skills add omnigent-ai/omnigent --skill otto-review-remediation -g -y
SKILL.md
Frontmatter
{
"name": "otto-review-remediation",
"description": "Handle trusted reviewers' change requests on Otto PRs."
}
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).
- 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.
- 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.
- Address every current substantive
CHANGES_REQUESTEDitem 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. - 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. - Continue through CI/mergeability (Resolve: Step 4.2) and the shared
otto-pr-review-loopskill (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. - 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.
- 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_urlso those comments stay linked. - Finish with the normal handoff using
mode: "review_remediation". Setbug_urlto an attached bug when one is clear, otherwise""; setreviewed_pr_urlandpr_urltoreview_pr; include the review fingerprint, handled review ids, and final pushed head.
Version History
- 369359f Current 2026-10-18 17:57


