Project Autopilot — Git skill for Claude Code
Give it a request: it plans, codes, reviews and tests the work with your coding-agent CLIs (Claude Code, opencode, Codex, Antigravity), then leaves the change for you to commit.
How to install Project Autopilot
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open mmetwally-dev/project-autopilot and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Project Autopilot does
Give it a request: it plans, codes, reviews and tests the work with your coding-agent CLIs (Claude Code, opencode, Codex, Antigravity), then leaves the change for you to commit. Works with SpecKit projects and checks browser tasks with Playwright.
Alternatives in Git
- Migration Plan: Merge Maps-scraper-pro Into Google-maps-scraper — Migration Plan: Merge maps-scraper-pro into google-maps-scraper skill 3.5k ★
- Fix GitHub Issue — by jeremymailen - Analyzes and fixes GitHub issues using a structured approach with GitHub CLI for issue detai 708 ★
- Memorix — Open-source cross-agent memory layer for coding agents via MCP 392 ★
README
Project Autopilot
Give it a request. It plans, codes, reviews and tests the work with your coding agents, until it passes.
A real 14-minute run, sped up. Left: ap run; right: the live watch report.
Project Autopilot (`ap`) runs a team of AI coding agents on your repository. You write what you want in one sentence. Autopilot gives each step to a different agent and checks every result before it moves on:
Planning → Plan Review → Implementation → Code Review → Gate (your tests) → Verification → Final Review → you commit
- A planner writes the plan and a task list.
- A plan reviewer checks the plan. The planner fixes it until the reviewer approves.
- An implementer codes the tasks, one task per session.
- A code reviewer checks each phase. The implementer fixes what it finds.
- Your test suite (the gate) runs after each phase.
- A verifier checks the phase against the plan and the test results.
- A final review checks the whole change once at the end.
Each role can be a different CLI and model, for example Claude Code for planning and review and a free opencode model for coding. The reviewers run read-only, and **Autopilot never commits or pushes**: when the mission is done, the changes wait in your working tree for you to review and commit.
**Works with:**
- SpecKit — if your project uses SpecKit (`.sp
Related Skills
Dev Agent Autopilot
Codex plans, Claude Code builds, Codex reviews, you merge. A project-agnostic development orchestrator for Cla
Agent Intern
MCP bridge that drives four coding CLIs — Google's Antigravity (agy), OpenAI Codex, GitHub Copilot, and Cursor
Coding Proxy
A High-Availability, Transparent, and Smart Multi-Vendor Proxy for Claude Code. Support Claude Plans, GitHub C
Workflow X
Showcase of workflow-x, the pro edition of workflow-dev: a Claude Code agent that takes your story end to end,
Build Task
Ticket to PR. Reads the Jira ticket, plans, stops for approval, then builds, tests, documents, pushes, opens t
Agent Loop Runtime
Headless runtime for running coding agents (Codex, Claude Code, Devin, Qwen Code, OpenCode, Aider, custom CLIs
Related Agents
Paf Reviewer
Runs one phone-a-friend relay or review command in the background and reports back a receipt plus the findings
Protocol Researcher
Verifies facts about vendor agent CLIs, SDKs, protocols and terms (Claude Code, Codex, Gemini CLI, OpenCode, A
Agent Of Empires
Claude Code, OpenCode, Mistral Vibe, Codex CLI, Gemini CLI Coding Agent Terminal Session manager via tmux and