autoresolve-oldest-github-issue

Select the oldest eligible GitHub issue and resolve it through merge with quality gates.

Updated Aug 15, 2025
One-click install
npx skills add https://github.com/pekral/pekral.cz --skill autoresolve-oldest-github-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoresolve-oldest-github-issue
Source: https://github.com/pekral/pekral.cz/tree/main/.claude/skills/autoresolve-oldest-github-issue
Command: npx skills add https://github.com/pekral/pekral.cz --skill autoresolve-oldest-github-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual overhead of triaging and driving GitHub issue resolution by automatically selecting the globally oldest eligible open issue and completing the full resolve-to-merge workflow with quality gates.

Core Features & Use Cases

  • Oldest-issue selection: Finds the globally oldest open GitHub issue (optionally filtered by a label), ensuring deterministic “oldest first” behavior rather than just picking from the newest batch.
  • End-to-end resolution chain: Executes the delegated resolution step, then performs GitHub code review, processes review feedback, and attempts a guarded merge.
  • Safety-first stopping: Stops and reports the blocker if merge conflicts occur, CI fails, approvals are missing, or Critical/Moderate findings remain—never force-merging.

Quick Start

Run autoresolve-oldest-github-issue with the default label Resolve_by_AI to resolve and (if safe) merge the oldest eligible open GitHub issue in the repository.

Frequently Asked Questions about autoresolve-oldest-github-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate resolving the oldest open GitHub issue end-to-end?

Automating oldest GitHub issue resolution requires selecting the globally oldest eligible open issue by ascending creation-time, then delegating the fix, code review, and guarded merge to downstream skills with safety checks.

Can I filter which GitHub issues get automatically resolved by label?

Yes, you can constrain automated issue resolution by applying a label filter, such as the default 'Resolve_by_AI', so the workflow only selects the oldest open issue matching that specific label.

What happens if an automated GitHub issue PR has failing CI or merge conflicts?

If failing CI, merge conflicts, missing approvals, or unresolved Critical/Moderate findings occur, the automated resolution workflow stops and reports the blocker immediately without force-merging.

How does oldest-issue selection work for automated GitHub triage?

Oldest-issue selection for GitHub triage searches open issues by ascending creation-time to find the globally oldest eligible issue deterministically, rather than picking from the newest batch.

Does automated PR merge require GitHub code review and CI gates to pass?

Yes, automated PR merge requires passing GitHub code review, processing review feedback, and clearing CI gates, stopping safely if approvals are missing or Critical/Moderate findings remain unresolved.