Software & DevOpsDone with Devin
Hand narrow code changes to Devin for pull requests
A team used Devin for a month on small fixes like chart formatting and API edge cases, with tests and PRs; a complex full-stack task went poorly.
- What They Did
- The RunLLM team connected Devin to their GitHub repo. It scanned the code and tried the setup steps. They typed short task descriptions, such as a pie chart format fix, an API edge case, and a default update schedule. Devin planned, edited, ran linters and tests, and opened a PR. The team spent about five minutes testing each result, and PR comments could steer further changes.
- How It Went
- Small single-component tasks took a minute or two to write up and five minutes to test, against roughly an hour by hand. A full-stack task with a new table, API call and button failed, and the team rewrote it themselves.
- Worth Knowing
- Small tasks cost 1-5 ACUs ($2-10) at $500 for 250 ACUs. The three larger tasks averaged about 20 ACUs, and two of them gave nothing usable.
Try it yourself with Devin
In the repo [repo URL], fix [small, well-defined issue, e.g. chart axis formatting or an API edge case with null input]. Add or update tests, make sure they pass, and open a pull request with a clear description of the change. Keep the scope narrow and don't refactor unrelated code; stop and ask me if the task looks bigger than described.
Do this with a skill.
These SkillShop playbooks do this exact job.