Menu
Master orchestrator to resolve a PR by diagnosing state and delegating to specialized skills.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | pr-resolver |
| description | Master orchestrator to resolve a PR by diagnosing state and delegating to specialized skills. |
| metadata | {"sideEffect":{"kind":"merge_pull_request","owner":"agent","outcomeArtifact":"var/pr_resolver/result.json","terminalContractId":"pr_resolver_terminal.v1","terminalSchemaVersion":"moonmind.pr-resolver-result.v1"},"publish":{"mode":"auto","owner":"agent","requiresEvidence":true,"verifyRemoteHead":"exact"},"required-skills":"fix-comments fix-ci fix-merge-conflicts","required-capabilities":["git","gh"],"implementation":{"contract":"pr-resolver-core/v1","supportedHosts":["cli"],"nativeHostEligible":false}} |
You are the master orchestrator for finishing Pull Requests. Use bounded retries to keep finalize resilient, and delegate actual fixes to specialized skills (fix-merge-conflicts, fix-comments, fix-ci) when blockers are actionable.
The task is not complete until the target PR is merged or is proven already merged. A local fix, local commit, passing local test run, unresolved review reply, or unpushed branch is not a successful PR resolution.
attempts_exhausted, unless a hard timeout, hard failure, or
non-retryable blocker is reached first.ci_running finalize waits use at least 60 seconds before the next check,
even when finalizeBackoffSeconds is lower.gemini-code-assist, the
resolver treats that as a Codex-review grace window and polls for up to 10
minutes before merging. Any additional visible comment/review ends the grace
wait immediately.This resolved Skill bundle is the sole semantic implementation of
pr-resolver, in MoonMind and outside it. The instructions in this file and the
portable helpers beside it own GitHub snapshot collection, comment retrieval,
comment actionability, CI interpretation, blocker priority, retry decisions,
specialized-skill selection, merge gating, and terminal-result construction.
MoonMind must execute this Skill through the ordinary agent Skill path. Native integration may resolve and materialize the immutable Skill bundle, provide the workspace and credentials, launch and supervise the runtime, enforce timeout or cancellation policy, capture logs, and persist or validate terminal artifacts. It must not replace any behavior listed above with MoonMind-only workflow, activity, adapter, or GitHub-client logic. In particular, MoonMind must not collect or classify PR comments on behalf of this Skill.
If a host cannot execute the resolved Skill bundle and its required Skills, it
must fail before mutation. It must never substitute a built-in implementation
based on the pr-resolver name, source, publish mode, or an implementation
metadata flag.
Resolve the active pr-resolver directory and use only the helpers from that
immutable active Skill set. Resolve fix-comments, fix-ci, and
fix-merge-conflicts from the same active set; do not use repo-global or
host-native substitutes. MoonMind exports the active root as
MOONMIND_ACTIVE_SKILLS_DIR. Outside MoonMind, set PR_RESOLVER_SKILL_DIR to
the directory containing this SKILL.md. Establish the portable paths before
running a helper:
PR_RESOLVER_SKILL_DIR="${PR_RESOLVER_SKILL_DIR:-${MOONMIND_ACTIVE_SKILLS_DIR:+$MOONMIND_ACTIVE_SKILLS_DIR/pr-resolver}}"
ACTIVE_SKILLS_DIR="${MOONMIND_ACTIVE_SKILLS_DIR:-$(dirname "$PR_RESOLVER_SKILL_DIR")}"
test -n "$PR_RESOLVER_SKILL_DIR" && test -f "$PR_RESOLVER_SKILL_DIR/SKILL.md"
Run the finalize gate checker. It refreshes PR metadata, CI, and the complete comment inventory before deciding whether merge is allowed:
python3 "$PR_RESOLVER_SKILL_DIR/bin/pr_resolve_finalize.py" \
--pr <pr_number_or_branch> \
--merge-method <merge|squash|rebase> \
--strict-exit-codes
Read var/pr_resolver/result.json and perform exactly the indicated action:
merged or independently verified already_merged: publish terminal
evidence and stop. A successful gh pr merge request is not terminal
evidence until a fresh gh pr view reports state=MERGED; merge-queue or
still-open states remain transient.merge_conflicts: the PR either conflicts with or is behind its base
branch; follow fix-merge-conflicts completely to merge the latest
origin/main, then push the synchronized branch.ci_failures: follow fix-ci completely.actionable_comments: follow fix-comments completely, including fresh
comment retrieval, its disposition ledger, push verification, and resolving
handled current review threads on GitHub.ci_running, codex_review_grace_wait, or another documented transient:
wait with the bounded backoff configured by the Skill inputs, then return to
step 2.manual_review or failed evidence and stop without merging.After every remediation, verify the exact local HEAD is visible on the PR
branch, then return to step 2. Never reuse a pre-remediation snapshot.
Enforce maxIterations, finalizeMaxRetries, and
finalizeMaxElapsedSeconds. Retryable/no-progress states receive at least five
finalize checks unless the elapsed-time limit or a hard failure is reached.
Before reporting success, generate artifacts/publish_result.json from the
final resolver result with the shared publish-evidence helper.
Allowed successful terminal states:
var/pr_resolver/result.json has status=merged, merge_outcome=merged, and mergeAutomationDisposition=merged.mergeAutomationDisposition=already_merged.Every terminal var/pr_resolver/result.json MUST include mergeAutomationDisposition:
merged: the resolver merged the PR.already_merged: the PR was independently confirmed as already merged.reenter_gate: the current resolver child completed a typed handoff to its
validated MoonMind.MergeAutomation parent. Include gatedContinuation with
the reason and an absolute UTC notBefore deadline when the next cycle must
wait. For Codex review grace, the direct finalizer copies the snapshot's
original codexReviewGrace.expiresAt; it never restarts that deadline.
Standalone resolvers cannot use this disposition successfully. Provider,
authentication, rate-limit, infrastructure, timeout, cancellation, stale
evidence, and malformed evidence failures are never cleared by continuation
metadata; only the synthetic PR_RESOLVER_REENTER_GATE classification may be
cleared by an authorized handoff.manual_review: the resolver stopped on a blocker, exhausted attempts, or needs human follow-up.failed: the resolver hit a hard execution failure.Everything else is blocked, failed, or still in-progress. In particular, never finish with task complete or a success summary when:
gh pr merge failed,Long waits have exactly two supported ownership patterns: keep the resolver command in the foreground with periodic progress, or write the authoritative typed continuation and return control to a validated merge-automation parent. Never start detached polling, emit the final agent response, and claim the poll will continue after the managed CLI exits. Background task identifiers in output have no lifecycle authority.
After any local commit-producing remediation, verify the exact current HEAD is visible on the remote PR branch before continuing. If git push, gh, or any GitHub connector path cannot publish the commit, stop as blocked with reason publish_unavailable; do not proceed to finalize and do not report success.
Never print raw environment variables while diagnosing GitHub auth or publish failures. Use targeted checks such as test -n "$GITHUB_TOKEN" or trusted-tool health calls; do not run printenv, env, set, or equivalent commands that can expose secrets.
When a delegated remediation step cannot publish, overwrite var/pr_resolver/result.json before stopping so parent workflows do not report stale gate state. Use status=blocked, merge_outcome=blocked, mergeAutomationDisposition=manual_review, reason=publish_unavailable, final_reason=publish_unavailable, and next_step=manual_review.
merge_conflicts, including a conflict-free PR reported as BEHIND, selects
fix-merge-conflicts once.ci_failures selects fix-ci once.actionable_comments selects fix-comments once.After a specialized Skill finishes, pr-resolver independently re-runs its
portable gate against the remote PR head. A remediation Skill must not claim
outer-loop success based on local commits, process output, or its own artifact
alone.
python3 "$PR_RESOLVER_SKILL_DIR/bin/pr_resolve_finalize.py" --pr <pr_number_or_branch> --merge-method <merge|squash|rebase>
python3 "$PR_RESOLVER_SKILL_DIR/bin/pr_resolve_full.py" --pr <pr_number_or_branch> --merge-method <merge|squash|rebase> --max-iterations <maxIterations>
pr_resolve_finalize.py as a gate checker; do not add remediation mutations there.attempts_exhausted and stop.task.publish.mode = "auto" and may commit, push, or merge only as required to resolve the target PR. Before reporting success, ensure artifacts/publish_result.json exists. The orchestration command normally generates it by running:
python3 "$ACTIVE_SKILLS_DIR/_shared/publish_evidence.py" from-pr-resolver-result \
--result var/pr_resolver/result.json
pr_resolve_orchestrate.py is a portable utility for non-agent automation and
tests. An agent executing this markdown owns specialized-skill dispatch and
must follow the workflow above rather than assuming that utility can perform
agent remediation.Discover open Dependabot version-bump PRs and enqueue one `pr-resolver` workflow for each.
Refresh MoonMind services from git by fetching and pinning a branch snapshot, pulling compose images, then restarting changed containers with optional orchestrator inclusion.
Provide the shared fan-out engine used by provider-specific Jira and GitHub batch presets to enqueue child workflows with inherited runtime and stable evidence.
Verify a GitHub issue against the current repository state, then post a GitHub issue comment with a PASS, PARTIAL, FAIL, or BLOCKED verdict. Works in two modes: (a) feature-branch mode, comparing a checked-out branch to its base ref; or (b) main/trunk mode, verifying that an issue is already implemented on the current default branch. Optionally close the issue as completed after a PASS. Use when a user asks whether a branch or merged change completes a GitHub issue, or needs an issue-visible verification comment.
Resolve GitHub PR feedback end-to-end for the branch you are on. Use when you need to fetch all comments on the branch PR, evaluate whether each comment still applies, decide whether it should be addressed, implement fixes, run compile/tests with retry-on-failure, then commit and push the result.
Create Jira issues such as tasks, stories, bugs, or subtasks from user intent. Use when a user asks to open, file, draft, or create a Jira ticket and needs fields validated, issue text composed, Jira API or connector calls made, and the created issue link returned.