cookys/autopilot

The AI project lead for your terminal.
Claude Code is the full home base. Autopilot plans, delegates, reviews with a second engine, and remembers what it learned — with portable paths for Codex, OpenCode, and agy where their harnesses support them.
Distilled from 100+ completed AI-development projects.
text
# autopilot's optional pre-push hook:
❯ git push
[autopilot] completeness scan … ✗ TODO stub in auth.py:42
[autopilot] tests … ✗ 1 skipped (payment flow)
[autopilot] review … ⚠ unhandled error path
push blocked — fix it, or override with a reason
## What Is Autopilot?
Claude Code is still the most complete host. Autopilot makes AI coding agents finish the job — the planning, checking, deciding, and remembering you'd otherwise do by hand:
Hand it the goal, get back a result — /l3 /l4 /l5 /l6 and ceo-agent can take a task end-to-end (sized, planned, built, reviewed, closed) and only stop to ask at the decisions that actually matter.
A second engine argues with your code — reviews can run on a different model family (GPT, Gemini), so more bugs get caught before your users see them instead of being rubber-stamped by the same model that wrote them.
Catches the "done" that isn't — a no-stub/no-TODO scan, your tests, and a real code review, run in the quality gate before you merge (and in the optional pre-push hook above).
Remembers, so your repo doesn't rot — captures the lessons, tracks the project, tells you what to do next, and adapts to your repo from a single markdown file in .claude/.
It ships first as a Claude Code plugin — 28 skills, 3 methodology agents, 25 hooks, zero dependencies — and keeps the same methodology portable where other harnesses expose compatible skill, agent, or plugin surfaces. It works fully on its own, and also plays nicely with the superpowers plugin if you have it.
> This README was written by Claude and adversarially reviewed by GPT-5.5 and Gemini through Autopilot's own second-engine review flow.
> New here? This page is the 5-minute tour. Everything deeper lives in Learn More.
## A Day With Autopilot
dev-flow is the front door. It sizes the task and routes it — small things go straight through the gate, large things become a tracked project:
Without Autopilot, Claude starts grep-ing the codebase immediately — no plan, no phases, no quality gates. With it, the discipline is automatic.
## Quick Start
bash
/plugin marketplace add cookys/autopilot
/plugin install autopilot@autopilot
That's it. Now just talk to Claude — Autopilot's skills trigger on what you say:
You: "I'm starting on WebSocket compression" → sizes it, sets up a plan + branch + quality gates
You: "quick fix for the null check in auth" → fast path, still gated before commit
You: "what should I work on next?" → scans your projects and ranks them
You: "搞定這個重構，你決定" → full autonomous CEO mode
No commands to memorize — say it in your own words and the right skill steps in.
## Choose Your Path
Autopilot is Claude Code-first, but not Claude Code-only. Pick the entry point that matches the harness you actually use:
| If you are... | Start with | What you get |
| Claude Code user | The two-command install above | The complete path: skills, methodology agents, hooks, /l3-/l6, and plugin-managed defaults |