Turn ticketed work into PRs and repair failing checks

Cognition used Devin to turn Slack and Linear requests into pull requests, then keep fixing review and CI issues until checks passed.

Done with Devinยท Intermediate

What they did
Cognition connected Devin to its repositories, then had staff mention it in Slack or on Linear and Jira tickets, sometimes with files attached. Devin searched the code, made a plan, and opened a pull request with a Devin Review link. When review tools or GitHub bots found problems, Autofix updated the PR, and Devin kept working through CI and lint failures until the checks were green. Humans still reviewed the pull requests.
How it went
Cognition merged 659 Devin pull requests in one week, compared with 154 in its strongest week earlier in 2025. The setup depended on clear, narrow tasks; work that needed deeper testing had to be split up and backed by verification.
Tips
Use this best for specific tasks with obvious success criteria. For anything risky or hard to test, add a separate verification step before merge or release.

Try it yourself with Devin

You are working in [repo name]. Use [Slack thread / Linear ticket / Jira issue] to understand the task, inspect the relevant code, and plan the smallest safe change. Implement it, open a pull request, and include a short summary of what changed and why. If review comments, bot findings, CI, or lint checks show problems, fix them and update the PR until all checks pass. Before you request reviewers, merge, delete, or submit anything, pause and show me the PR summary and wait for my approval.

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

Read the original on nader.substack.com โ†—

Get 3 agent uses like this every morning

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