Create a pull request that follows the project's template and title conventions. Check existing behavior and test coverage, document testing limits, and coordinate self-review or bot review with follow-up on reported issues.
- Create a PR using the project's required template
- Check regression tests and coverage for new behavior
- Request bot review when local testing is limited
Significant-Gravitas/AutoGPT☆ 187.7KUpdated Oct 23, 2026
Coordinate multiple Claude Code agents in separate Git worktrees and tmux windows. Assign tasks, inspect progress, help stalled agents resume, and verify PR checks and review feedback before treating work as complete.
- Assign separate development tasks to multiple agents
- Check agent progress and available worktrees
- Help stalled or crashed agent sessions resume
Significant-Gravitas/AutoGPT☆ 187.7KUpdated Oct 23, 2026
Compare performance across releases, environments, or time windows using Sentry data. Report request counts, latency percentiles, and failure rates, with statistical checks that distinguish faster or slower behavior from noise and flag insufficient data.
- Compare performance before and after a release
- Compare a preview deployment with a control
- Check other operations for performance regressions
Significant-Gravitas/AutoGPT☆ 187.7KUpdated Oct 23, 2026
Work through PR review feedback by fixing code, pushing commits, replying to reviewers, and resolving addressed threads. Monitor automated checks, merge conflicts, and new comments until checks pass and the review work is complete.
- Fix code based on PR review feedback
- Reply to human and bot reviewers
- Investigate failed CI checks after a push
Significant-Gravitas/AutoGPT☆ 187.7KUpdated Oct 23, 2026
Prepare a pull request for merging by repeatedly reviewing changes and addressing feedback. Verify resolved discussions, passing automated checks, and mergeability, then check twice for late comments after the checks finish.
- Preparing a pull request for merging
- Repeating review and fixes until no new issues remain
- Following up on delayed review bot feedback
Significant-Gravitas/AutoGPT☆ 187.7KUpdated Oct 23, 2026
Review a pull request, a proposed code change, for correctness, security, design, and test coverage. Check its explanation and existing feedback, then post findings on relevant code lines with severity labels.
- Checking a pull request before merging
- Reviewing security risks in code changes
- Finding missing edge-case tests
Significant-Gravitas/AutoGPT☆ 187.7KUpdated Oct 23, 2026