batch-pr-resolver

name	batch-pr-resolver
description	Discover open PRs in a repository and enqueue one `pr-resolver` task for each.
metadata	{"sideEffect":{"kind":"enqueue_children","owner":"agent","outcomeArtifact":"artifacts/batch_pr_resolver_result.json"},"required-capabilities":["gh"]}

Batch PR Resolver Skill

Purpose

Create one queue task per open pull request so each PR branch can be resolved by pr-resolver on its existing branch. Fork PRs are skipped.

This parent batch skill does not publish repository changes itself. It records child workflow queueing evidence in artifacts/batch_pr_resolver_result.json; each queued pr-resolver child owns its repository publishing outcome.

Inputs (skill args)

• repo (string, required): Target repository in owner/repo form.
• state (string, optional): PR state filter for discovery. Default is open. Using other states prints a warning.
• includeForks (boolean, optional): Reserved for compatibility. Currently rejected because queued pr-resolver jobs cannot reliably check out fork-only head refs.
• skipExistingOnly (boolean, optional): Legacy alias kept for compatibility. If set, skip PRs from fork repositories. Note: this name is counter-intuitive; true means forks are skipped.
• maxAttempts (number, optional): Queue job maxAttempts for each created task. Default 3.
• priority (number, optional): Queue job priority. Default 0.
• mergeMethod (string, optional): Merge method passed to pr-resolver. Default squash.
• maxIterations (number, optional): pr-resolver loop cap. Default 5.
• runtimeMode (string, optional): Runtime to stamp onto each queued pr-resolver task. When omitted, the helper falls back to inherited task context or deployment defaults.
• runtimeModel (string, optional): Explicit model override to stamp onto each queued pr-resolver task.
• runtimeEffort (string, optional): Explicit effort override to stamp onto each queued pr-resolver task.
• runtimeProviderProfile (string, optional): Explicit provider-profile override to stamp onto each queued pr-resolver task.

Workflow

1. Run the helper script:

python3 .agents/skills/batch-pr-resolver/bin/batch_pr_resolver.py \
  --repo <owner/repo> \
  --state <open|merged|closed> \
  --skip-existing-only \
  --max-attempts 3 \
  --priority 0 \
  --merge-method squash \
  --max-iterations 3 \
  --runtime-mode <runtime_mode> \
  --runtime-model <model> \
  --runtime-effort <effort> \
  --runtime-provider-profile <profile_id>

2. Map inputs to flags:

   • repo -> --repo
   • state -> --state
   • skipExistingOnly -> --skip-existing-only
   • includeForks -> --include-forks (currently rejected at runtime)
   • maxAttempts -> --max-attempts
   • priority -> --priority
   • mergeMethod -> --merge-method
   • maxIterations -> --max-iterations
   • runtimeMode -> --runtime-mode
   • runtimeModel -> --runtime-model
   • runtimeEffort -> --runtime-effort
   • runtimeProviderProfile -> --runtime-provider-profile

   Always forward the parent task's explicit runtime selection fields when they are present so the queued pr-resolver tasks reuse the same runtime, model, effort, and provider profile instead of falling back to the deployment default runtime.

3. For each open PR in the target repo:

   • Skip PRs identified as cross-repository (isCrossRepository=true) or whose head is not on owner/repo.
   • Build a canonical queue task with:
     • type: "task"
     • payload.idempotencyKey: stable per parent batch run and PR, hash-backed and capped to the execution persistence limit, so rerunning the same batch task does not create duplicate resolver workflows.
     • payload.repository: target repo
     • payload.task.git.startingBranch: PR head branch
     • payload.task.publish.mode: auto
     • payload.task.skill.name: pr-resolver
     • payload.task.inputs: { repo, pr, branch, mergeMethod, maxIterations }
   • Submit via the internal Temporal execution API (POST /api/executions), require the canonical workflowId in the response, and verify that ID via GET /api/executions/{workflowId} before counting it as queued; MOONMIND_URL must point at the MoonMind API from the managed session.

4. Write one summary artifact at batch_pr_resolver_result.json under the managed session artifact spool path when available, otherwise under the configured --artifacts-dir.

5. On any submission or verification error, write skill_outcome.json with a failed or partial status so the managed runtime cannot report the batch as successful.

6. Print a short count summary to stdout (queued, skipped, errors).

Safety constraints

• Reject missing repo unless it can be inferred from git remote origin fallback.
• Use state=open by default to avoid accidental non-open PR dispatch.
• --include-forks is rejected to avoid unreliable fork-branch checkout behavior in queued jobs.
• Skip fork PRs by default.
• Require MOONMIND_URL to reach the MoonMind API; the legacy direct-DB queue fallback is intentionally unsupported.