meta-issue-to-pr-autopilot

Orchestrates issue triage, sub-agent fixes, and pull request creation via gh.

6.8k|540|Updated May 6, 2026
One-click install
npx skills add https://github.com/opensquilla/opensquilla --skill meta-issue-to-pr-autopilot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-issue-to-pr-autopilot
Source: https://github.com/opensquilla/opensquilla/tree/main/src/opensquilla/skills/exp/meta-issue-to-pr-autopilot
Command: npx skills add https://github.com/opensquilla/opensquilla --skill meta-issue-to-pr-autopilot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end workflow of turning a GitHub issue into an open pull request, removing the manual steps of reading the issue, implementing a fix, writing a PR description, and running gh commands. Note that it is currently deprecated and disabled pending a bounded sub-agent contract and side-effect ledger.

Core Features & Use Cases

  • Issue Fetching: Retrieves the referenced GitHub issue and gathers relevant repository context as the first pipeline step.
  • Delegated Fix Loop: Passes the issue to a sub-agent step that implements the code fix.
  • PR Drafting and Opening: Summarizes the patch into a PR description and opens the pull request via the gh CLI.
  • Use Case: A maintainer with a small, well-scoped bug report wants the agent to fetch the issue, produce a fix, and open a PR titled with the issue summary without manual intervention.

Quick Start

Ask the agent to take the linked GitHub issue, implement a fix with a sub-agent, and open a pull request with a generated description.

Frequently Asked Questions about meta-issue-to-pr-autopilot

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

FAQPage Schema
How do I automatically turn a GitHub issue into a pull request?

This meta-skill chains four steps: fetch the issue with repo context, delegate the fix to a sub-agent, summarize the patch into a PR description, and open the PR via the gh CLI. It is currently deprecated and disabled by default.

Why is the issue-to-PR autopilot skill disabled?

It is deprecated pending a bounded sub-agent contract and side-effect ledger. The skill lacks risk metadata enforcement, per-step budgets, and a rollback path, so it must not be re-enabled without high-risk metadata and a saga-style compensation step.

What permissions does an issue-to-PR automation workflow need?

This workflow requires four capabilities: vcs for git operations, filesystem-write for applying the fix, network-write for pushing and opening the PR, and subprocess for running the gh CLI. It is classified as high risk.

What kinds of issues work best with automated PR creation?

Small, well-scoped issues with clear acceptance criteria work best. Ambiguous or large issues produce unreliable sub-agent fixes, and the skill provides a manual fallback using gh issue view and gh pr create.

What is the manual fallback if the autopilot fails?

Manually run gh issue view to read the issue, implement the code fix yourself, write the PR body, and then run gh pr create to open the pull request.