autoresolve-oldest-github-issue

Constraints

• Apply @rules/git/general.mdc
• Apply @rules/reports/general.mdc
• Operate on the current Git repository's GitHub remote only — refuse if the remote is not GitHub
• Process exactly one issue per invocation; never loop into a second issue
• Never bypass quality gates of the delegated skills (resolve-issue, code-review-github, process-code-review, merge-github-pr)
• Code review is a hard merge gate (@rules/git/general.mdc Merging): never reach step 6 (merge) until steps 4–5 have run a code review on the PR's final diff and driven it to 0 Critical + 0 Moderate. A merge without a converged code review is forbidden — do not skip or reorder steps 4–5 to merge sooner.
• Never force-merge: stop on merge conflict, failing CI, missing approvals, or unresolved Critical/Moderate CR findings
• Never alter the original issue body, labels, or assignees outside what the delegated skills already do. Exception: resolve-issue applies the Resolve_by_AI:in-progress claim label at the start of work and releases it on a pre-PR Blocked/abort — this is a sanctioned write owned by the delegated skill, not a constraint violation.
• Do not expose sensitive/internal details in user-facing messages

Use when

• The user wants the oldest open GitHub issue auto-resolved end-to-end (resolve → review → process feedback → merge)
• A scheduled or batch workflow needs a single deterministic entry point that chains the four skills

Inputs

• LABEL (optional) — GitHub label used to filter eligible issues. Default: Resolve_by_AI. Pass an empty string (LABEL="") to disable label filtering and pick the globally oldest open issue.

Execution

1. Preflight

• Confirm gh auth status reports an authenticated session; if not, stop and ask the user to authenticate.
• Resolve the current Git remote origin and verify it points to GitHub. Stop with a clear message otherwise.
• Switch to the main branch and pull the latest changes.

2. Select the oldest issue

• Resolve the current repository slug: REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner).
• Query the single oldest open issue via gh search issues, which — unlike gh issue list — supports explicit ascending order and therefore returns the globally oldest match regardless of total open-issue count:

  CLAIM_LABEL="${CLAIM_LABEL:-Resolve_by_AI:in-progress}"
  QUERY="is:open is:issue repo:${REPO}${LABEL:+ label:\"$LABEL\"} -label:\"${CLAIM_LABEL}\""
  gh search issues "$QUERY" --sort created --order asc --limit 1 \
      --json number,url,title,createdAt,labels,assignees
  

  The -label: negation excludes any issue already carrying the Resolve_by_AI:in-progress claim label, so two parallel autoresolve runs always select different issues. CLAIM_LABEL defaults to Resolve_by_AI:in-progress and can be overridden to match a repository that uses a custom claim label. Do not substitute gh issue list --sort created --limit <N>: that command returns the newest N issues with no --order switch, so any client-side ascending sort picks the oldest of the newest, never the true oldest.
• If the result is empty, stop with the message No eligible open GitHub issues found (label=<LABEL>).
• Record the selected issue's number and url. This URL is the single argument passed to every downstream skill in the chain.