autopilot

Automate end-to-end PR triage and iteration without merging.

2|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/enkira-ai/claude-plugins --skill autopilot-enkira-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autopilot
Source: https://github.com/enkira-ai/claude-plugins/tree/main/plugins/autopilot/skills/autopilot
Command: npx skills add https://github.com/enkira-ai/claude-plugins --skill autopilot-enkira-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the overnight PR grind by triaging open PRs, polling for updates, and addressing reviewer feedback, enabling users to keep PRs moving toward a ready-to-merge state without manual intervention.

Core Features & Use Cases

  • Open and monitor PRs from ready issues, surface blockers, and summarize review threads.
  • Address reviewer comments automatically when aligned with the RFC, providing rationales for replies when out of scope.
  • Poll CI status and ensure no merges occur until all checks are green, adhering to a "ready to merge" stop condition.

Quick Start

Invoke /loop /autopilot:autopilot to run continuous overnight PR processing.

Frequently Asked Questions about autopilot

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

FAQPage Schema
How do I automate overnight GitHub PR triage and code review responses?

Automating overnight PR triage involves processing open pull requests, reading linked issues, and applying RFC-approved changes to address reviewer feedback. This workflow automation runs continuous loops to poll updates and move PRs toward a ready state without manual intervention.

What is RFC-grounded decision making in automated pull request workflows?

RFC-grounded decision making uses approved design documents to validate requested code changes during PR automation. The system addresses reviewer comments automatically when they align with the RFC, providing rationales for replies when requests fall out of scope.

Can I use continuous automation to monitor CI status and block PR merges until checks pass?

Yes, the automation polls CI status continuously and enforces a strict stop condition to ensure no merges occur until all checks are green. This guarantees safe, non-merging automation loops that only prepare PRs to be ready for final approval.

Does autopilot workflow automation actually merge pull requests when CI is green?

No, the autopilot workflow does not merge pull requests. It applies approved changes and moves PRs toward a ready-to-merge state, stopping safely once all CI checks are green and reviewer feedback is resolved without executing the merge.

How do I start an automated loop for processing open GitHub pull requests?

Invoke /loop /autopilot:autopilot to run continuous overnight PR processing. This command initiates the automation loop that triages open PRs, monitors CI status, and iteratively addresses reviewer feedback based on linked RFCs and approved changes.

When should I avoid using automated PR triage and iteration workflows?

Avoid automated PR triage when pull requests lack linked issues or RFCs for grounding decisions, or when your workflow requires immediate merging upon CI success rather than preparing a ready-to-merge state for manual review and approval.