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.
Before opening the PR:
git push -u origin <branch>)This is critical. Before opening the PR, verify:
If you cannot run the full test suite locally, note which tests you ran and which you couldn't in the test plan.
Read the canonical PR template at .github/PULL_REQUEST_TEMPLATE.md and use it verbatim as your PR body:
cat .github/PULL_REQUEST_TEMPLATE.md### Why / What / How### Changes 🏗️### Checklist 📋<!-- ... -->) with actual content; do not leave them in- [ ] until each step is actually completedPR 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.
Use gh pr create with the base branch (defaults to dev if no [base-branch] was provided). Use --body-file to avoid shell interpretation of backticks and special characters:
BASE_BRANCH="${BASE_BRANCH:-dev}"
PR_BODY=$(mktemp)
cat > "$PR_BODY" << 'PREOF'
<filled-in template from .github/PULL_REQUEST_TEMPLATE.md>
PREOF
gh pr create --base "$BASE_BRANCH" --title "<type>(scope): short description" --body-file "$PR_BODY"
rm "$PR_BODY"
/pr-test to do E2E manual testing of the PR using docker compose, agent-browser, and API calls. This is the most thorough way to validate your changes before review./pr-review to self-review the PR for correctness, security, code quality, and testing gaps before requesting human review.This is common for agents running in worktrees without a full stack. In this case:
/pr-review locally to catch obvious issues before pushing/review on the PR after creating it to trigger the review botgh api repos/Significant-Gravitas/AutoGPT/pulls/{N}/reviews --paginate and the GraphQL inline threads query. The bot typically responds within 30 minutes, but polling lets the agent react as soon as it arrives./pr-address which has a full polling loop with CI + comment tracking# After creating the PR:
PR_NUMBER=$(gh pr view --json number -q .number)
gh pr comment "$PR_NUMBER" --body "/review"
# Then use /pr-address to poll for and address the review when it arrives
Once the review bot or human reviewers leave comments:
/pr-address to address review comments. It will loop until CI is green and all comments are resolved.| Skill | When to use |
|---|---|
/pr-test | E2E testing with docker compose, agent-browser, API calls — use when you have a running workspace |
/pr-review | Review for correctness, security, code quality — use before requesting human review |
/pr-address | Address reviewer comments and loop until CI green — use after reviews come in |
After the PR is created and review is triggered: