How to automate issue-to-pull-request coding with AI agents

7 real setups for issue-to-pull-request coding, most-discussed first. Steps come from each source; the full prompt is one click away.

Quick answer

7 real setups on agentsetups show how people automate issue-to-pull-request coding with AI agents. Agents used: Claude (3), Hermes Agent (1), GitHub Copilot (1), Codex (1), Grok Bot (1), Amp (1).

Fastest start (from Scan a 0.5M-line codebase, then auto-open refactor PRs by Pau Guirao):

  1. Scan the whole codebase for code quality and security issues. The author used the Jev model on about 0.5M lines.
  2. Feed the findings to Claude Code (Opus 5.5) running in a loop on a server so it is always on.
  3. The loop opens refactor PRs, runs the gates, and merges once the gates pass.

Last updated · based on 336 use cases on agentsetups, each credited to its author.

1. Scan a 0.5M-line codebase, then auto-open refactor PRs

A Jev scan found 12,938 issues in 2 min for $0.89; an always-on Opus 5.5 loop opens and merges refactor PRs (50 merged).

  1. Scan the whole codebase for code quality and security issues. The author used the Jev model on about 0.5M lines.
  2. Feed the findings to Claude Code (Opus 5.5) running in a loop on a server so it is always on.
  3. The loop opens refactor PRs, runs the gates, and merges once the gates pass.

Claude · by Pau Guirao (X post, 23 Sep 2026) · source

2. Let Hermes run PR reviews and client status updates

A 20-dev agency gave Hermes repo, IRC and Cloudflare access on a VPS; it now handles PR reviews, daily status and builds after approval.

  1. Run Hermes on one VPS with access to the team’s chat, repos and infrastructure.
  2. Have it act only after you say yes to its proposals.
  3. For each new task, first create a skill with test cases, then do the task.

Hermes Agent · tools: IRC, MCP · by /u/xbxz (Reddit, 17 Sep 2026) · source

3. Assign a GitHub issue to the Copilot coding agent

Treat it like an intern: put the log line in the issue, state the fix constraint, then request changes on the PR.

  1. Write the issue with the log line and the exact constraint (e.g. key on (delivery_id, attempt) or the business id; do not redesign the worker).
  2. Assign it to the coding agent and wait for the PR.
  3. Review it like an intern’s PR and request changes on noise.
  4. Variant (Jules): a precise 3-sentence ticket worked; a vague “clean up” ticket did not.

GitHub Copilot · tools: GitHub · by Equinox (X post, 2 Sep 2026) · source

4. Ship 40 PRs a day with a chief-of-staff agent team

A ChiefOfStaff, per-project PMs and a CodeMaster that prompts claude -p / codex CLIs on a VM, looping PRs to green.

  1. Talk only to a ChiefOfStaff agent, which works all the other bots.
  2. Give each project a PM agent that understands it in depth.
  3. PMs send requests to a “CodeMaster” that writes prompts for claude -p and codex CLI, and runs them only on a VM.
  4. Loop PRs until green, then merge.

Claude, Codex, Grok Bot · by Gabe Fletcher (X post, 9 Sep 2026) · source

5. Let Amp orbs pick up your team’s GitHub issues

Small projects on GitHub; Amp orbs monitor issues the team files; Puck handles simple tasks; Vercel deploys main.

  1. Host the codebase on GitHub.
  2. Have Amp orbs monitor GitHub issues as your team creates them.
  3. Treat Puck like an infra teammate for simple tasks.
  4. Deploy on Vercel with CI/CD publishing main.

Amp · tools: Vercel, Ollama · by AriesTheCoder (X post, 26 Sep 2026) · source

6. Write PR specs first, then build in parallel with Cline

Three people built a config-driven game: detailed PR descriptions, Plan mode before Act, and a setup PR that locked shared types.

  1. Before any code, write each PR’s description: files touched, rules, edge cases, what tests should check.
  2. Land one setup PR that locks in the shared types.
  3. Each person takes their own PRs into Cline, starts in Plan mode to confirm the approach, then switches to Act.
  4. Work in separate folders (engine, components, pages); connect everything in the last PR.

Cline · tools: Plan mode · by /u/Few-Ad-5053 (Reddit, 23 Sep 2026) · source

7. Ticket in, PR out: four skills and a reviewer in CI

Six weeks in: 128 PRs, 124 merged; planning a ticket takes about 12 minutes (self-reported).

  1. Write tickets with an agent, after it audits the code: Problem statement, acceptance criteria, dependencies; it shows you every ticket before creating it.
  2. Ask a read-only dispatcher what to work on next: It ranks tickets by how many others they unblock and lists your waiting PRs first; tiny shell allowlist, no subagents.
  3. Create one worktree per ticket yourself: Branch and directory named after the ticket (worktrunk); .env copied in by a hook.
  4. Run a read-only investigation that ends in a plan: Every acceptance criterion maps to a step; you approve the plan.
  5. Build test-first, then prove it in the browser: Failing test first; Playwright CLI walks each acceptance criterion with screenshots; PR includes human verification steps.
  6. Review every push with a context-fed CI reviewer: Claude Code in GitHub Actions, read-only, fed the PR history and the tickets as the spec.

+2 more steps in the copyable prompt.

Claude, OpenCode · by rogs (blog, 30 Sep 2026) · source

Questions people ask

Which AI agent is best for automating issue-to-pull-request coding?

In the 7 setups here, the agents named are Claude (3), Hermes Agent (1), GitHub Copilot (1), Codex (1), Grok Bot (1), Amp (1), Cline (1), OpenCode (1). That is what people used, not a quality ranking.

What do I need to automate issue-to-pull-request coding with an AI agent?

An agent (Claude, Hermes Agent, GitHub Copilot are the most common here). Each setup lists only the tools its source states.

Is there a prompt I can copy?

Yes. Every use-case page has a copyable prompt with the steps embedded and a “Based on” credit line, for example Scan a 0.5M-line codebase, then auto-open refactor PRs.

Related guides