---
name: oss-help
description: "Quick reference card for OSS Autopilot commands, agents, and workflows"
allowed-tools: Read
---

# OSS Autopilot Quick Reference

Print this reference card for the user. Do NOT run any commands — just display the information below.

---

## Commands

| Command | Purpose |
|---------|---------|
| `/oss` | **Daily check** — fetches open PRs, shows status dashboard, suggests actions (respond to reviews, fix CI, rebase, find new issues) |
| `/oss-search` | **Find issues** — multi-strategy search across GitHub for contributable issues matching your language/label preferences |
| `/setup-oss` | **Configure** — set GitHub username, languages, labels, PR limits, and other preferences |
| `/oss-dashboard` | **Dashboard** — open the interactive SPA dashboard in your browser |
| `/oss-guidelines` | **Guidelines** — view, edit, or reset per-repo contribution guidelines learned from past PRs |
| `/pr-ready` | **Pre-push gate** — run the lint/test/review convergence loop to decide whether the current branch is ready to push |
| `/plan-ready` | **Plan gate** — run the same review-and-critique convergence loop on an implementation plan before code is written |
| `/oss-help` | **This card** — quick reference for all plugin capabilities |

## Agents

These agents activate automatically when relevant, or you can ask for them directly:

| Agent | When to Use |
|-------|-------------|
| **pr-responder** | "Help me respond to comments on my PR" — drafts professional replies to maintainer feedback |
| **pr-health-checker** | "Why is my PR failing CI?" — diagnoses CI failures, merge conflicts, stale reviews, and performs rebases |
| **pr-compliance-checker** | "Check if my PR is ready" — validates against opensource.guide best practices before submission |
| **issue-scout** | "Find me issues to work on" — searches and vets good contribution opportunities |
| **repo-evaluator** | "Is this repo worth contributing to?" — analyzes maintainer responsiveness and project health |
| **contribution-strategist** | "How am I doing?" — analyzes contribution patterns and provides strategic advice |
| **pre-commit-reviewer** | "Review my changes before I push" — checks diffs for bugs, style issues, and dead code |

## Typical Workflow

```
1. /oss              → See what needs attention
2. Pick an action    → Respond to review, fix CI, rebase
3. /oss-search       → Find new issues when you have capacity
4. Pick an issue     → Work on it → Submit PR
5. /oss              → Monitor PR until merged
```

## Skills

Three sibling skills cover OSS contribution best practices:

- **oss-contribution** (index): universal rules — minimal-diff discipline, working on issues, time management, failure protocol.
- **pr-etiquette**: review-feedback responses, PR descriptions, dormant-PR follow-up cadence, PR quality checklist, communication style.
- **contribution-ethics**: AI attribution rules, AI-tell avoidance in maintainer-visible writing, when to defer to a human contributor.

## Optional: Enhanced Code Review

The pre-commit review workflow supports the **pr-review-toolkit** plugin for parallel specialized review (5 agents). Without it, the built-in `pre-commit-reviewer` handles all reviews. Both paths include iterative fix-and-re-review loops.

To install: search for `pr-review-toolkit` in the Claude Code plugin marketplace.

## Configuration

Settings are stored in `~/.oss-autopilot/state.json`. Run `/setup-oss` to reconfigure.

Key settings: GitHub username, max active PRs, dormant threshold, preferred languages, issue labels, squash preference.

### Session Start Health Check

On every session start, the plugin shows a one-liner PR status summary (e.g., "OSS: 15 active PRs — 3 need addressing, 12 waiting on maintainer (2h ago)"). This reads cached state from your last `/oss` run — no network calls.
