autopilot
Skill779 starsChanged 49 days agoMITView on GitHub
One tick of Vortix's automated lifecycle — resume unfinished work, keep main and open PRs green, triage new issues, build the next approved or bug issue end to end with fix-bug, prepare a release for the maintainer's approval, and verify it after it ships. Run it on a loop (`/loop /autopilot`); use it whenever the user asks to "run the project", "work the backlog", "keep going on your own" or "autopilot", even if they name no issue.
82 other projects use a version of this.
Adopted by
Most recently taken up by
- codeboehm/maximtheir own version, first seen Nov 16, 2026
- tjst-t/claude-skillstheir own version, first seen Nov 16, 2026
- GongYuanCaiJi/jobsalvotheir own version, first seen Nov 16, 2026
- BoredHF/albertskillstheir own version, first seen Nov 16, 2026
- Yomudogly/oh-my-agytheir own version, first seen Nov 16, 2026
- noelceta/content-enginetheir own version, first seen Nov 16, 2026
Used with
Projects with it also use review-bugbot, rename-chat and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
0mlkrizzz655335vSkillreview-bugbot
缺陷导向代码审查。用 Bugbot 子代理找 bug。
Also in 3 projects that use this
0mlkrizzz655335vSkillrename-chat
重命名当前聊天。按聊天内容改标题。"disable-model-invocation: true
Also in 3 projects that use this
Tsumugii24Skillsplit-to-prs
Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.
Also in 4 projects that use this
PandelisZSkillupdate-cli-config
View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.
Also in 3 projects that use this
32103210Skillmigrate-to-skills
Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when you want to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands into the skills directory.
Also in 3 projects that use this
32103210Skillupdate-cursor-settings
Modify Cursor/VSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.
Also in 3 projects that use this
- +1 more from 32103210
- +1 more from 0mlkrizzz655335v
Other versions82 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 82
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-codex★ 34ksame name
- SethGammon/Citadel★ 927same name
- H-mmer/pentest-agents★ 815same name
- nick-vels/skills★ 599same name
- yan-labs/yan-skills★ 307same name
- kentcdodds/kcd-skills★ 64same name
- Kanevry/session-orchestrator★ 53same name
- jantichy/claude★ 52same name
72 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- docs-reviewSkill
- fix-bugSkill
- ideateSkill
- release-changelogSkill
- release-qaSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 73 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 33
Do the first step below that has work, finish that one unit, report, and stop.
- Distinctive: line 59
4. Release: Follow "Release" below when it applies.
- Very specific: line 93
Run release-qa on main. A no-go finding is fixed through fix-bug before the freeze starts.
- Very specific: line 95
Run release-changelog; it writes the changelog onto the release PR.
- Distinctive: line 99
every commit by someone other than the maintainer or autopilot.
- Distinctive: line 107
Check the release page for all assets.
- Very specific: line 112
Stop the droplet's billing: scripts/vpn-lab.sh down --yes.
- Very specific: line 116
Stop and ask rather than guess.
- Very specific: line 120
Never merge a PR labelled release or proposal, never force-push, and never push to main.
“Common” is measured: kept by at least 6 in 10 of the 73 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Autopilot
Vortix runs itself except for two decisions the maintainer keeps:
- Ideation: what gets built. Only bugs and issues labelled
approvedare built. Ideas wait asproposaluntil the maintainer labels themapprovedordeferred(or decides in a/ideatesession). - Release: what ships. Autopilot prepares the release PR and says what is in it. Only the
maintainer merges it; a hook refuses a Claude merge of any PR labelled
release.
Everything between is automatic. Read CLAUDE.md first: every rule there binds each step
here.
State lives on GitHub
| Label | Meaning | Set by |
proposal | An idea waiting for the maintainer's yes or no | autopilot, /ideate |
approved | Build it | the maintainer |
in-progress | Autopilot is working on it; at most one issue at a time | autopilot |
blocked | Waiting on a person; the latest autopilot comment says who and for what | autopilot |
bug, enhancement, priority, security, deferred and good first issue keep their
meanings. Never remove a label the maintainer set.
One tick
Do the first step below that has work, finish that one unit, report, and stop. One unit per tick keeps the work serial: one branch, one PR, nothing racing.
0. Preflight. On main with a clean tree (git status); gh auth status shows
Harry-kp active; the lab answers (ssh … true); tmux vxrun exists. Only when this tick
will connect a real tunnel: scripts/vpn-lab.sh ensure (docs/live-testing.md "Test VPN servers"). A missing machine
does not stop the tick, but a step that needs it does: the live checks in fix-bug, and
release-qa. Skip those steps and name the missing machine in the report.
1. Resume. An issue or PR labelled in-progress: continue it where the branch and its
PR show it stopped.
2. Main is red. The latest main run of any workflow failed (gh run list --branch main
--limit 10): fix-bug with the failing run as the report. A flake gets one
gh run rerun --failed first.
3. Open PRs. Oldest first:
- Autopilot's own: failing checks or unanswered review comments → fix, push, re-check.
- A contributor's: run the
revieweragent on it. Clean and green → merge (gh pr merge --squash --delete-branch) and thank them. Findings → one review comment with all of them. Changes to.github/,scripts/,Cargo.tomldependencies,unsafe, subprocess calls or network destinations →blockedfor the maintainer, never merged by autopilot. - Dependabot majors (minors merge themselves): green and the changelog breaks nothing Vortix
uses → merge; otherwise
blocked.
4. Release. Follow "Release" below when it applies.
5. Triage. Each open issue with no autopilot comment and none of the state labels:
- A bug: reproduce it (
fix-bugstep 3). Not enough to go on → ask the reporter one precise question and labelblocked. Reproduced → leave it for step 6 with a comment saying so. - An idea or feature request: label
proposaland comment with the problem it solves, the evidence that users hit it, the smallest version worth building, what it costs (code, TUI density, upkeep) and a recommendation. No building. - A question: answer it with links to the docs; close it when answered.
- A duplicate: close it, linking the original.
6. Build. The next buildable issue: open, not deferred, blocked, proposal or
good first issue (left for contributors). Order: security, then priority, then other
bugs, then approved features; oldest first within each. Label it in-progress, then run
/fix-bug <n> (its "Approved feature" section covers features). After the merge, remove
in-progress. Two failed attempts at the same step → blocked with what was tried and what
is needed.
7. Propose. Nothing above had work and fewer than three proposal issues are open: open
one well-argued proposal from real signals (reactions and comments on open issues, repeated
questions, deferred items whose reason has changed). Never build it.
Nothing to do anywhere: report that in one line.
Release
When: release-plz's PR (label release) is open, main holds a user-visible change since
the last tag, nothing is in-progress, and either a security or priority fix has merged
or the last release is 7 or more days old.
Freeze first. From here until the release PR merges, merge nothing else into main:
release-plz rewrites the changelog on every push. The freeze is on while the release PR branch
carries a docs: user-facing changelog commit.
- Run
release-qaonmain. A no-go finding is fixed throughfix-bugbefore the freeze starts; if one appears after, fix it on the release branch the wayrelease-qasays. - Run
release-changelog; it writes the changelog onto the release PR. Comment on the release PR, titled What ships in vX.Y.Z, with:
- the changelog section;
- the QA verdict and anything not run;
- every commit by someone other than the maintainer or autopilot;
- anything known and not fixed.
Then send a push notification: "vX.Y.Z is ready for your review:
<PR link>".- The maintainer merges, or comments. A comment is a change request: address it, update the What ships comment, and notify again.
After it ships (a new tag, and the release PR merged):
- Check the release page for all assets.
- Bring up the test VPN servers (
scripts/vpn-lab.sh ensure, docs/live-testing.md "Test VPN servers"), then check the install channels:P0_TAG=vX.Y.Z P0_SMOKE=0 scripts/p0-vms.shon the lab. - A failure is a
prioritybug. Open it and fix it throughfix-bug. - Comment the result on the release PR. Issues fixed in the release are closed by their PRs.
- Stop the droplet's billing:
scripts/vpn-lab.sh down --yes.
Rules
- Stop and ask rather than guess. Label the item
blocked, write the question as a comment, and move on to other work. Don't wait. - Notify the maintainer only at the two gates, or when every remaining item is blocked on them.
- Any comment that asks something of the maintainer mentions @Harry-kp.
- Never merge a PR labelled
releaseorproposal, never force-push, and never push tomain..claude/settings.jsondenies or guards each of these.
Report
One line per tick: what was done, with the link, and what comes next. Example:
Built #354 (help mentions h/l): PR #361 merged. Next: triage #362.
Running it
In a tmux window on the Mac, next to vxrun:
cd ~/Documents/personal/vortix && claude
/loop /autopilotThe loop paces itself: it is short while there is work and long when the queue is empty. The
lab and vxrun must be up for live checks and release QA.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

