Turn Slack feedback into pull requests with an agent

Use an agent to sort Slack feedback, draft fixes as PRs, and help debug infrastructure with read-only access.

Done with Devin· Advanced· Sep 2026

What they did
A company routed every user complaint and feature request from a dedicated Slack channel to Devin. The agent sorted the messages, talked with users inside Slack to shape issues into pull requests, and handled async-flow and infrastructure debugging without write access. Engineers mainly reviewed and merged, while non-technical teammates helped write PRs.
How it went
Sid Nanda said they ended up among the top 200 Devin users worldwide. The setup was costly, but the fast payoff made the premium worthwhile, and Devin Review helped catch useful bugs.
Tips
Keep the agent on read-only access when you want it to investigate systems but not make changes. Have it show a triage list and draft PRs first, then wait for approval before any merge or reply.

Try it yourself with Devin

Watch [Slack channel] for feedback over the last [timeframe]. Sort each message into bugs, feature requests, and questions, then rank the items you can address in [repo]. For the highest-priority items, draft one pull request per issue and summarize the changes. If you need to inspect production or infrastructure, use read-only access only. Before you post any Slack reply, open a PR, merge anything, send a message, or delete code, stop and ask me to approve the next step. Show me the triage list, the draft PRs, and any debugging findings first.

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

Read the original on x.com ↗

Get 3 agent uses like this every morning

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