pr-create
Create Pull Request
Steps
- Check for existing PR:
gh pr view --json url -q .url 2>/dev/null— if a PR already exists, output its URL and stop - Understand changes:
git status,git diff dev...HEAD,git log dev..HEAD --oneline - Read PR template:
.github/PULL_REQUEST_TEMPLATE.md - Draft PR title: Use conventional commits format (see CLAUDE.md for types and scopes)
- Fill out PR template as the body — be thorough in the Changes section
- Format first (if relevant changes exist):
- Backend:
cd autogpt_platform/backend && poetry run format - Frontend:
cd autogpt_platform/frontend && pnpm format - Fix any lint errors, then commit formatting changes before pushing
- Backend:
- Push:
git push -u origin HEAD - Create PR:
gh pr create --base dev - Output the PR URL
Rules
More from significant-gravitas/autogpt
pr-review
Review a PR for correctness, security, code quality, and testing issues. TRIGGER when user asks to review a PR, check PR quality, or give feedback on a PR.
43vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
30worktree
Set up a new git worktree for parallel development. Creates the worktree, copies .env files, installs dependencies, and generates Prisma client. TRIGGER when user asks to set up a worktree, work on a branch in isolation, or needs a separate environment for a branch or PR.
21pr-address
Address PR review comments and loop until CI green and all comments resolved. TRIGGER when user asks to address comments, fix PR feedback, respond to reviewers, or babysit/monitor a PR.
21backend-check
Run the full backend formatting, linting, and test suite. Ensures code quality before commits and PRs. TRIGGER when backend Python code has been modified and needs validation.
17pr-test
E2E manual testing of PRs/branches using docker compose, agent-browser, and API calls. TRIGGER when user asks to manually test a PR, test a feature end-to-end, or run integration tests against a running system.
16