Skip to content
Agentguiden.no
Submit your own

A GitLab issue becomes a draft, then a PR

u/MountainByte_Ch has 11 years of experience and let a dotnet program and Claude Code take issues assigned to him. He edits draft replies before posting. A ready issue becomes a branch and a PR. He reads everything. After a week he spends about 2-3 hours a day on review.

Done with Claude CodeAdvanced

What was done

On 10 April 2026 u/MountainByte_Ch writes in r/ClaudeAI that he is a developer with 11 years of experience. About 80 percent of the job is put on a dotnet program and Claude Code. The program fetches issues assigned to him in GitLab. An issue is classified, and Claude Code starts with the repo, the images and the description. If the issue is not ready, he saves a draft and edits it before it is posted. If it is ready, a subagent takes the summary, does the work, pushes a new branch and opens a PR for him. The loop also checks whether the issue has a PR, whether there are new comments, and applies the comments. It runs on a loop of 15 minutes. Every 1 minute the mouse is moved, so he does not go inactive in Teams and the machine does not turn off. It has run for a week. He writes that the quality is about what he would otherwise have shipped, because he reads everything. He now spends about 2-3 hours a day on review and testing.

How it went

The PRs are opened for him, and he reads the changes. Replies that are not ready are not posted until he has edited the draft. The post does not say how many issues went through that week.

Worth knowing

"About 80 percent" and "about 2-3 hours" are his words. The quality is his comparison, not a measurement in the post. The mouse move is what he uses to keep Teams active. The prompt below does not ask you to do that.

How to do it

  1. Let the agent read the issue and say whether it is ready.
  2. If it is not ready, take the draft and edit it yourself before posting.
  3. If it is ready, read the branch and the PR. Do not push and do not post before you have said yes.

Try it with Claude Code

Read issue [number] in [repo]. If it is not ready, write a reply as a draft here. If it is ready, describe the change. Do not push, do not open a PR and do not post until I say yes.

Replace text in brackets with your own.

Done when. You have read the draft or the diff, and nothing has been pushed or posted without a yes.

Safety rule. The agent does not push, does not open a PR and does not post until you say yes.

Read the original

Read the original · u/MountainByte_Ch on Reddit ·

  • A first app approved after a month

    The author built his first app in Replit, with ChatGPT for the planning. The build took less than a week. Approval took a month.

    ReplitNewreddit.com

  • Grok built 8 terminal games side by side

    u/pzarevich watched Grok build 8 terminal games in C in agenc-core, one task per game. The orchestrator gathered and checked them at the end. A transfer from a Ledger device requires physical approval. He does not say a transfer was made.

    GrokNewreddit.com

  • Agent builds run on Windows VMs

    bentcorner let the agents build and test over SSH on WSL in remote Windows VMs. The Mac is no longer used for those build runs.

    Valgfri agentNewnews.ycombinator.com

  • Codex installed Claude Code and asked for a review

    u/Bulldagshunter had Codex work through a defect review. Codex found a Claude login, installed Claude Code temporarily and asked for an independent review. The first pass was stuck in plan mode. The second pass ran tests in a sandbox, with the Nexus library outside. He thinks Codex should have asked first.

    CodexNewreddit.com

Five agents a day

A short daily email with five concrete examples of AI agents. Nothing else.