Skip to main content
Tag Devin on a GitHub issue the same way you’d tag a teammate. When any user comments /devin on an issue, this automation spins up a session that reads the full issue context, searches the codebase for the relevant files, implements the fix with tests, and opens a pull request that references the issue — closing the loop from bug report to code change.

Use this template

Open /devin Issue Fix in Devin and create the automation with the default configuration. You can customize it before saving.

​
What this automation does

The /devin command turns your GitHub issues list into a queue of actionable work. Instead of triaging tickets, estimating, and assigning, an engineer (or even a non-engineer) can drop a one-line comment and walk away. Devin handles investigation, implementation, test coverage, and PR creation end-to-end.

​
How it works

Trigger: Github event — issue.comment
  • Event: github:issue_comment
    • Conditions:
      • action eq created
      • comment.body starts_with /devin
      • comment.user.login neq devin-ai-integration[bot]
      • repository.full_name eq your-org/your-repo
What Devin does: Starts a session with full event context, executes the prompt below, and (optionally) notifies you on failure.

​
Prerequisites

​
Example prompt

The template ships with this prompt. You can edit it after clicking Use template, or leave it as-is.

​
Setting it up

  1. Open Automations → Templates in Devin.
  2. Click /devin Issue Fix. The create page opens with this template pre-filled.
  3. Connect any required integrations and install MCP servers if you haven’t already.
  4. Replace any placeholder values in the trigger conditions (for example, swap your-org/your-repo for your actual repo).
  5. Review the prompt and adjust it for your team’s language, conventions, and guardrails.
  6. Click Create automation.
Most automation templates include suggested ACU and invocation limits to bound cost during early rollout. Keep them as-is until you’re confident in the automation’s behavior, then raise them to fit your workload.

​
When to use this template

  • Community-reported bugs that have a clear reproduction step
  • Small feature requests with well-defined acceptance criteria
  • Documentation fixes, typos, and trivial stylistic changes
  • Giving non-engineer teammates a frictionless path to ship fixes

​
Customization ideas

  • Restrict to a set of repositories or GitHub organizations
  • Require the commenter to be a collaborator (add a condition on comment.author_association)
  • Forward to a playbook that encodes your team’s fix conventions
  • Pair with Bug Report Triage so Linear bugs route through the same fix flow

​
See also