costajohnt/oss-autopilot

---
If you contribute to more than a couple of projects, PRs go stale without you noticing. A maintainer asks for a change, CI breaks after a rebase, a branch picks up a conflict, and you find out two weeks later.
OSS Autopilot checks every open PR you have on GitHub and sorts them into what needs you and what is waiting on someone else. For the ones that need you, it helps draft the reply, diagnose the CI failure, or rebase the branch. You approve each push and each comment before it goes out.
Contents
- Requirements
- Quick start (Claude Code)
- Other ways to run it
- The daily check
- Commands
- Finding new issues
- Overnight mode
- Dashboard
- Configuration
- How it works
- What it will and will not do on its own
- Troubleshooting
- Limitations
- Contributing
Requirements
- Node.js 22 or newer
- GitHub CLI installed and logged in (gh auth login), or a GITHUB_TOKEN in your environment
- For the plugin: Claude Code, plus npm and network access on first run (see below)
CI runs on Ubuntu and macOS. Windows is untested.
Quick start (Claude Code)
Restart Claude Code, then:
Setup asks for your GitHub username, the languages and labels you care about, and how many PRs you want open at once. After that, run /oss whenever you want to check in.
**About the first run.** The plugin ships as source. The first /setup-oss or /oss installs dependencies and builds the CLI inside the plugin directory, so it needs npm (or pnpm) and a network connection, and it takes longer than later runs. If the build fails, see Troubleshooting.
Other ways to run it
MCP server (Cursor, Claude Desktop, Codex, Windsurf, any MCP client)
Save your GitHub username once:
Then add the server to your MCP client config:
The MCP server exposes 30 tools, 6 resources, and 4 prompts. @latest means you get new releases automatically; pin a version (@oss-autopilot/mcp@5.7.4) if you would rather update on your own schedule.
Standalone CLI
Every command accepts --json and returns { success, data, error, timestamp }, so it is easy to script.
As a library
API reference: jcosta.tech/oss-autopilot.
The daily check
1. Run /oss.
2. The CLI fetches your open PRs from GitHub and classifies each one: failing CI, changes requested, unanswered maintainer comment, merge conflict, incomplete checklist, or waiting on the maintainer.
3. You get a short list with the PRs that need you first, and a menu of actions.
4. Pick one. An agent reads the thread and the diff, then drafts a reply or prepares a fix.
5. You read the draft and approve, edit, or discard it. Nothing is pushed or posted until you approve that specific action.
6. Repeat, or stop. Most days this is a few minutes.
If you are new to this, set maxActivePRs to 3 to 5. A few PRs you respond to quickly do better than many you let sit.
Commands
The plugin adds 9 slash commands:
| Command | What it does |
|---------|--------------|
| /oss | Daily check: what needs attention, then an action menu |
| /oss-search | Find issues to work on, matched to your languages and history |
| /oss-overnight | Unattended run that prepares fix branches locally and writes a morning report |
| /oss-dashboard | Open the local dashboard in your browser |
| /oss-guidelines | View or edit what the tool has learned about each repo's review preferences |
| /pr-ready | Pre-push loop: lint, tests, parallel review agents, fix, repeat until clean |
| /plan-ready | The same review loop for an implementation plan, before you write code |
| /setup-oss | Configure preferences |
| /oss-help | Quick reference |
**Commands:** /oss, /oss-search, /oss-overnight, /oss-dashboard, /oss-guidelines, /pr-ready, /plan-ready, /setup-oss, /oss-help
The plugin also ships 8 specialized agents that Claude dispatches for you:
| Agent | Job |
|-------|-----|
| pr-responder | Drafts replies to maintainer feedback |
| pr-health-checker | Diagnoses CI failures, conflicts, stale reviews; rebases when needed |