# Open a Pull Request

Open a PR with the template, tests and bot review when local testing is limited.

- Repository: https://github.com/Significant-Gravitas/AutoGPT (187858 stars)
- Category: Git and review
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Significant-Gravitas/AutoGPT --skill open-pr -g -a claude-code -y`
Codex: `npx skills add Significant-Gravitas/AutoGPT --skill open-pr -g -a codex -y`
Cursor: `npx skills add Significant-Gravitas/AutoGPT --skill open-pr -g -a cursor -y`
Gemini CLI: `npx skills add Significant-Gravitas/AutoGPT --skill open-pr -g -a gemini-cli -y`

## Description

Open a pull request with proper PR template, test coverage, and review workflow. Guides agents through creating a PR that follows repo conventions, ensures existing behaviors aren't broken, covers new behaviors with tests, and handles review via bot when local testing isn't possible. TRIGGER when user asks to "open a PR", "create a PR", "make a PR", "submit a PR", "open pull request", "push and create PR", or any variation of opening/submitting a pull request.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Open a Pull Request

## Step 1: Pre-flight checks

Before opening the PR:

1. Ensure all changes are committed
2. Ensure the branch is pushed to the remote (`git push -u origin <branch>`)
3. Run linters/formatters across the whole repo (not just changed files) and commit any fixes

## Step 2: Test coverage

**This is critical.** Before opening the PR, verify:

### Existing behavior is not broken
- Identify which modules/components your changes touch
- Run the existing test suites for those areas
- If tests fail, fix them before opening the PR, do not open a PR with known regressions

### New behavior has test coverage
- Every new feature, endpoint, or behavior change needs tests
- If you added a new block, add tests for that block
- If you changed API behavior, add or update API tests
- If you changed frontend behavior, verify it doesn't break existing flows

If you cannot run the full test suite locally, note which tests you ran and which you couldn't in the test plan.

## Step 3: Create the PR using the repo template

Read the canonical PR template at `.github/PULL_REQUEST_TEMPLATE.md` and use it **verbatim** as your PR body:

1. Read the template: `cat .github/PULL_REQUEST_TEMPLATE.md`
2. Preserve the exact section titles and formatting, including:
   - `### Why / What / How`
   - `### Changes 🏗️`
   - `### Checklist 📋`
3. Replace HTML comment prompts (`<!-- ... -->`) with actual content; do not leave them in
4. **Do not pre-check boxes**, leave all checkboxes as `- [ ]` until each step is actually completed
5. Do not alter the template structure, rename sections, or remove any checklist items

**PR title must use conventional commit format** (e.g., `feat(backend): add new block`, `fix(frontend): resolve routing bug`, `dx(skills): update PR workflow`). See CLAUDE.md for the full list of scopes.

The rest: https://github.com/Significant-Gravitas/AutoGPT/blob/HEAD/.claude/skills/open-pr/SKILL.md