- Tackling many tasks in parallel, before they end up in your backlog Linear/Jira tickets
- Entire features from scratch
- Bug reports
- App testing
- Code migrations, refactors, and modernization Language migrations (e.g. JavaScript to TypeScript)
- Framework upgrades (e.g. Angular 16 -> 18)
- Monorepo to submodule conversions
- Removing unused feature flags
- Extracting common code into libraries
- Common, repetitive engineering tasks PR Review
- Codebase Q&A
- Reproducing & fixing bugs
- Writing unit tests
- Maintaining documentation
- Customer engineering support Building new integrations and working with unfamiliar APIs
- Creating customized demos
- Prototyping solutions
- Building internal tools
- Write clear prompts with explicit completion criteria — the clearer the task, the higher the success rate, especially for complex work.
- Make tasks easy to verify — e.g. checking that CI passes or testing an automatic deployment.
- For harder tasks, break them into well-scoped steps and provide relevant context or examples.
- Follow our best practices and pre-task checklist .
- Tagging Devin on a Slack or Teams thread about a bug you’re discussing with coworkers
- Delegating a more complex task via the web application and taking over in Devin’s IDE once it gives you a good first draft.
- Running Devin for Terminal in your local environment for quick fixes, code exploration, and interactive coding right from the command line — then using /handoff to send longer tasks to cloud Devin.
- Carving out tasks from your todo list at the start of your day and returning to draft PRs waiting for review.
Devin: What are Devin’s strengths?
First seen · Cognition