autopilot

Automate GitHub issues through resolution, PR creation, verification, and sign-off.

421|49|Updated Jul 3, 2014

Search Tags:#code review #github #issue management #development automation #pr creation

Ready to run

npx skills add https://github.com/joshukraine/dotfiles --skill autopilot-joshukraine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: autopilot
Source: https://github.com/joshukraine/dotfiles/tree/main/claude/.claude/skills/autopilot
Command: npx skills add https://github.com/joshukraine/dotfiles --skill autopilot-joshukraine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the development process by autonomously carrying GitHub issues through the entire development loop, from issue resolution to PR creation or deployment.

Core Features & Use Cases

Autonomous Dev Loop: Handles steps like issue resolution, code simplification, PR creation, verification, walkthrough, code review, local CI, and sign-off.
Tiered Execution: Stops at PR-ready or continues to merge+deploy based on the specified tier.
Use Case: For a well-specified issue, use /autopilot to automate the entire workflow without manual intervention, saving time and reducing errors.

Quick Start

Run the autopilot command with the issue number: /autopilot [issue-number] [--to pr|merge].

Frequently Asked Questions about autopilot

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

FAQPage Schema

How do I automate GitHub issue resolution from start to PR creation?▼

To automate GitHub issue resolution, use a development automation tool that executes the full workflow: issue resolution, code simplification, PR creation, verification, and sign-off. This eliminates manual intervention for well-specified issues.

Can I automatically merge and deploy after a GitHub pull request is created?▼

Yes, you can automatically merge and deploy after a PR is created by setting a tiered execution parameter. The workflow continues past PR-ready to handle merging and deployment autonomously without further manual input.

What steps does autonomous GitHub issue processing include?▼

Autonomous GitHub issue processing includes issue resolution, code simplification, PR creation, verification, walkthrough, code review, local CI, and sign-off. These steps execute sequentially to drive issues to a PR-ready or merge and deploy state.

Do I need a well-specified GitHub issue to automate the development loop?▼

Yes, you need a well-specified GitHub issue to automate the development loop. The automation relies on clear issue definitions to accurately execute code changes, PR creation, and verification without requiring manual intervention or clarification.

What is the best way to streamline GitHub issue workflow without manual coding?▼

The best way to streamline GitHub issue workflow is using a tiered automation command that drives the entire dev loop. It handles issue resolution through merge and deploy, reducing manual coding effort and errors for well-defined tasks.

When should I not use automated development loops for GitHub issues?▼

You should not use automated development loops for GitHub issues that lack well-defined specifications. The automation requires clear parameters to execute code simplification and PR creation accurately, making ambiguous issues unsuitable for this workflow.