issue-to-merged-pr

Automate GitHub issue-to-PR workflows with CI feedback and post-merge cleanup.

4|1|Updated Feb 4, 2024
One-click install
npx skills add https://github.com/Arx-Game/arxii --skill issue-to-merged-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-to-merged-pr
Source: https://github.com/Arx-Game/arxii/tree/main/tools/skills/issue-to-merged-pr
Command: npx skills add https://github.com/Arx-Game/arxii --skill issue-to-merged-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, git, claude, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Automates the end-to-end GitHub issue workflow from initial pickup through a merged PR, coordinating design, implementation, CI, and post-merge cleanup with minimal human gating.

Core Features & Use Cases

  • Detect issue type from labels, generate a branch, and draft a spec on the issue body.
  • Implement plan steps, synchronize with main, push a PR, watch CI, and perform CI fixes if needed.
  • After merge, file follow-up issues and link them to the PR for traceability.

Quick Start

Tell Claude Code to work on an issue to start carrying it through to a merged PR.

Frequently Asked Questions about issue-to-merged-pr

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

FAQPage Schema
How do I automate a GitHub issue from pickup to merged PR with CI feedback?

You can automate the GitHub issue-to-PR workflow by using Claude Code orchestration to coordinate branch generation, plan implementation, CI monitoring, and post-merge cleanup with minimal human gating.

Can I use Claude Code to automatically fix failing CI on a pull request?

Yes, Claude Code orchestration watches CI status after pushing a PR and performs automated CI fixes if checks fail, ensuring the pull request progresses toward merge without manual intervention.

How do I generate a branch and draft a spec from GitHub issue labels?

The automation detects the issue type from labels like feature, fix, chore, or refactor, generates a corresponding branch, and drafts an implementation spec directly on the issue body.

Do I need the Claude Superpowers plugin to run the issue-to-PR workflow?

Yes, the issue-to-PR automation requires the Claude Superpowers plugin along with gh, git, and jq installed, using GitHub as the source of truth with no on-disk persistent state.

What happens after a pull request is merged in the automated GitHub workflow?

After a PR is merged, the automation files follow-up issues and links them to the merged PR for traceability, completing the end-to-end issue resolution process.

How does the GitHub issue automation handle multi-invocation progression?

The Claude Code-driven orchestration manages multi-invocation progression, coordinating each phase from initial issue pickup through design, implementation, CI feedback, and final post-merge cleanup.