Issue to PR
An engineering workflow that takes an issue, gathers context across the codebase and traces, and proposes a pull request — or a runbook step when code change is not the right move.
Most engineering issues fall into a handful of patterns: bump a dependency, fix a flaky test, add a missing log line, document an undocumented field. An agent with the right context and the right tool surface can propose a PR — for a human to review, not to merge unattended.
What it solves
Compresses the time between an issue being filed and a credible first attempt at a fix. Surfaces issues that are not really code issues earlier.
How we build it
GitHub or GitLab MCP tools with scoped repo access; retrieval over the codebase and recent commits; trace context for issues that arrived through observability. The agent opens a PR, runs the test suite, and posts a summary with reasoning. A human reviews, merges, requests changes, or closes.
- Repo MCP tools with scoped access
- Codebase retrieval and recent-commit context
- Test execution before PR open
- Human-reviewed merge gate
What changes when it is in place
The team's review-to-merge ratio shifts toward more reviewable, smaller PRs. Issues that are documentation gaps or runbook gaps surface as such instead of dragging through engineering.