Devin use cases

Cap how many issues are assigned to agents at once, for example per reviewer. Assign only small, well-specified issues with a test command. Decide in advance when to finish a pull request by hand and when to close it, and close stale ones on a schedule. Put each repeated review comment into AGENTS.md or CLAUDE.md so the next pull request avoids it. Track merge and close rates per kind of task, and stop assigning kinds that rarely merge.

Give the agent the current docs: paste the upgrade guide or changelog, or connect a docs MCP server. Add short notes on changed APIs to CLAUDE.md or AGENTS.md. Tell it the exact versions from your lockfile. Run the type checker and tests after every change, so wrong calls fail fast. When the agent proposes a migration step, ask for the doc link that describes it.

Say in the prompt that tests and assertions must not be changed, deleted or skipped without your approval, and that a failing test that looks wrong means stop and ask. Record the test count before the agent starts and compare it after. Review the test diff before the code diff. Run the suite yourself rather than trusting the agent's summary, or have CI post the result. For new tests, check that each one fails without the change. Mutation testing shows whether the tests catch real bugs.