autopilot
English | 中文
Claude Code slash commands for running JS/TS fullstack work unattended, driven to genuine 100% completion — then graded independently. Plus /demo-video, which records the finished work as a demo video, and /flow-check, which walks the app as a real user and reports where the flow can be shorter.
/autopilot <task or spec-path> — adopts a strict completion condition as a standing directive: maps every layer (FE/BE/API/DB/auth/tests/build), forbids self-authored scope-narrowing, runs the repo's real verification matrix, verifies in a real browser, and only stops when every requirement line is [LIVE]-verified or [BLOCKED] by a real external dependency. Built for when you're away and can't answer follow-ups./autopilot-eval [run-dir] — grades a finished run hands-on: it does not trust the run's own summary. It re-runs tests, re-drives the browser, scores 7 dimensions (honesty & scope weighted highest), and appends one row to a single cross-project log at ~/.claude/autopilot-eval.md./make-review-prompt [requirements|code] [target] — generates a self-contained adversarial review prompt you can hand to a fresh agent or a human reviewer, targeting either a requirements/spec doc (before coding) or a code change (before merge). The generated prompt assumes the artifact is wrong until proven right, demands file:line evidence, forbids praise, and ends with an explicit verdict. Pairs naturally with /autopilot: stress-test the spec before the run, stress-test the diff after it./autopilot-auto <task> [--session <id>] [--max-rounds N] [--timeout H] — combines /autopilot coding with an automated adversarial review loop powered by OpenAI Codex (CLI or Cursor plugin). You open two sessions — Claude Code for coding, Codex for reviewing — enter the same session ID on each side, and walk away. They communicate through a shared channel file (.autopilot/reviews/<session-id>/channel.md), polling every minute. The loop terminates when Codex approves, max rounds (default 10) are reached, or timeout (default 5h) expires. See How to use /autopilot-auto below./demo-video [mode=clip|walkthrough] [lang=en|zh] [voice=…] [music=…] … — records a real demo video of a web app with scripted Playwright: a clip (15–30 s proof of one fix or feature for a ticket or PR, with a before cut for bug fixes) or a walkthrough (minutes long, chapters, fast-forwarded waits, captions, optional English voice-over and music). It rehearses before recording, ends on the app's real result, keeps secrets out of frame, and an independent reviewer subagent must pass the cut before delivery. See How to use /demo-video below./flow-check [feature | all] [flow|ux|recheck] [out=<dir>] — a flow-minimalist product review done in a real browser: it walks each user goal from the most likely starting point using only what is on screen, counts steps, pages, decisions and long waits, and asks of every step can it be removed, merged, automated or deferred? Each finding is ranked P0–P3 with a concrete fix and a browser-checkable "done when". The full report and screenshots go to a flow-check-<date>-<topic>/ folder in the checked repo; the chat gets a short summary. It never changes code. See How to use /flow-check below.
These are opinionated and intentionally strict. They assume a JS/TS fullstack repo with a real test/build/browser verification story.
Prerequisite — give it a well-designed spec. /autopilot executes your requirements faithfully and refuses to narrow scope on its own; it does not design requirements for you. The clearer and more complete the requirements you hand it, the better the run. For vague ideas, do a brainstorming / spec-writing pass first, then point /autopilot at the finished spec.
Install
Option A — Claude Code plugin (recommended for sharing)
/plugin marketplace add ocxers/autopilot
/plugin install autopilot@bruce-plugins
Then invoke namespaced:
/autopilot:autopilot <task or spec-path>
/autopilot:autopilot-eval
/autopilot:make-review-prompt
/autopilot:autopilot-auto <task> [--session <id>] [--max-rounds N] [--timeout H]
/autopilot:demo-video [mode=clip|walkthrough] [lang=en|zh] …
/autopilot:flow-check [feature | all] [flow|ux|recheck] [out=<dir>]
To update later (/plugin install won't refresh an already-installed plugin):
/plugin marketplace update bruce-plugins
/plugin update autopilot@bruce-plugins
Or skip manual updates entirely: run /plugin, open the Marketplaces tab, and enable auto-update for bruce-plugins — new versions then install automatically on startup.
Option B — install script (keeps the bare /autopilot)
Symlinks the commands into ~/.claude/commands/ and the demo-video and flow-check skills into ~/.claude/skills/, so you keep the un-namespaced names:
git clone https://github.com/ocxers/autopilot.git
cd autopilot
./install.sh # symlink (default) — git pull auto-updates the commands
./install.sh --copy # copy instead of symlink
./install.sh --uninstall
Then invoke:
/autopilot <task or spec-path>
/autopilot-eval
/make-review-prompt [requirements|code] [target]
/autopilot-auto <task> [--session <id>] [--max-rounds N] [--timeout H]
/demo-video [mode=clip|walkthrough] [lang=en|zh] …
/flow-check [feature | all] [flow|ux|recheck] [out=<dir>]
If ~/.claude/skills/demo-video or ~/.claude/skills/flow-check already exists as a real directory (your own copy), the script leaves it alone and says so; move it away and re-run to use the repo version.
The script also seeds an empty eval log at ~/.claude/autopilot-eval.md if you don't already have one. It never overwrites an existing log.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
