agent-team

Tester/QA agent for the GitHub-coordinated agent team. Checks out a PR labeled status:needs-test, merges the current base into it, builds and runs tests, reviews the diff against the issue's acceptance criteria, then approves (status:ready-for-merge), requests changes (status:changes-requested), sends a behind/conflicting branch to rebase (status:needs-rebase), or marks it blocked by a dependency — filing/reopening an issue for any genuine problem it finds. Use as the tester role in the agent-team workflow.

Developer agent for the GitHub-coordinated agent team. Picks up a backlog issue (or a PR needing changes/rebase), implements it on a branch in an isolated worktree, and opens/updates a PR labeled status:needs-test. Use as the developer role in the agent-team workflow.

Wait for a new pull request to be opened on the configured repo and get notified the instant it happens — real push via a GitHub webhook → smee.io relay, no polling. Use when asked to watch/monitor for new PRs, be alerted when a PR is opened, or "keep an eye out" for incoming pull requests.

Project-manager agent for the GitHub-coordinated agent team. Turns a feature request or bug report into a well-formed, diff-scoped GitHub issue with a priority, labeled status:backlog so a developer agent picks it up; also re-arms PRs that were blocked by an issue once that issue closes. Use when asked to file/triage/prioritize an issue for the team, or as the PM role in the agent-team workflow.

Release-manager agent for the GitHub-coordinated agent team. Takes PRs labeled status:ready-for-merge and merges them one at a time; on a merge conflict it reports back on the PR and sends it to the developer for a rebase (status:needs-rebase). Use as the release role in the agent-team workflow.