Pull Requests
Use pull requests to connect code changes to the work they complete, review, or unblock.
What appears
The pull request view lists open pull requests across connected version control tools such as GitHub and GitLab. GitLab merge requests appear in the same list. Selecting a pull request opens details such as branch, description, review status, and linked work.
When agent work is tied to a pull request or merge request, the detail view shows related agent sessions and activity.
In spec-driven development, the pull request should point back to the initiative, bug, todo, or synced issue it came from. That keeps review, completion, recaps, and roadmap progress tied to the same source.
GitHub PR bot
The GitHub PR Bot can write a structured summary at the top of a pull request and update it as commits change. Summaries usually include an overview, details by area, related tickets, impact checklist, and review focus checklist. PR Bot activity also feeds pull request analytics such as volume, lead time, cycle time, review lag, and merge rate.
Use Pull Request Flow to measure review and merge health after PRs are linked to work.