Use Devin to draft pull requests on a codebase

A team tested Devin on their codebase for PR creation, but slow output and full review needs made it feel like a junior developer.

Done with Devin· Intermediate· Jan 2025

What they did
A commenter’s team at a fairly large tech company gave Devin access to their codebase and asked it to prepare pull requests. It did produce PRs, but the process was slow, and people still had to check the code themselves. In practice, the tool stayed in the loop as a helper rather than taking work off the team’s plate.
How it went
They stopped using it because the pace was too slow and the benefit did not justify the extra review work. The commenter also said the pricing did not stack up. Their impression was that it was roughly on par with bringing on a junior developer.
Tips
If you try this, test it on a narrow slice of work first and measure both turnaround time and review effort. The main tradeoff to watch is whether the agent saves enough time to offset the cost and the manual checking.

Try it yourself with Devin

In [repository name], take on [ticket or bug description]. Make the code change, run the relevant tests, and prepare a pull request with a brief explanation of the approach and any risks. Before you create, push, or submit anything, pause and show me the plan, the diff, and any open questions so I can approve it first.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on reddit.com ↗

2 more reports of this

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.