Turn recurring feedback into tested pull requests

A developer used a Dot to spot repeated customer requests, make small fixes, test them, and return draft pull requests with demo clips.

Done with Dots· Intermediate· Sep 2026

What they did
A developer set a Dot loose on customer feedback inside its connected cloud workspace. It looked for repeated asks, chose small bug fixes or improvements, then built and tested each change. When it finished, it handed back complete pull requests along with videos showing the edits, while the developer kept working on the next big feature.
How it went
This was presented as an example, so there were no measured results or counts. The caution was that Dots can still make mistakes, so anything important needs a human review before it goes further.
Tips
Keep the task narrow and ask for draft PRs first. Have it pause for your approval before any merge, push, or other irreversible step.

Try it yourself with Dots

Watch [feedback source] for requests that show up repeatedly. For each recurring issue, pick a small fix in [repo name], implement it, run the relevant tests, and prepare a draft pull request with a short video showing the change and a brief note linking it back to the feedback. Stop after [number] pull requests and show me the drafts for review before you merge, push, submit, delete, or send anything.

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

Get 3 agent uses like this every morning

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