Skip to main content
Don’t want to set this up manually? Paste a link to this page into a Devin session and ask it to set everything up for you.
1

Write a docs skill

Start by creating a skill for the task you want to standardize. In this example, we’ll build a skill that generates API documentation whenever a team member labels a ticket.Go to Customize > Skills and click + (New skill). Name it add-docs.Write specific, step-by-step instructions. Reference real file paths and conventions so Devin follows your team’s standards:The more specific your skill, the better the output. Reference your team’s actual doc templates, style guides, and tooling. See Writing a good skill for more.
2

Sync the skill to Linear

Connect your Linear integration if you haven’t already: go to Settings > Connections > Linear and click Connect. Select the teams Devin should have access to.Once connected, scroll to Skills and click Add skill. Select add-docs from the dropdown. This creates the skill’s label in Linear, in the Devin Skills label group; the Skills list shows the label to use (@skills:add-docs when no other synced skill has that name) with a button to copy it.Now when anyone adds that label to a ticket, Devin starts a session using your skill.
For skill labels to sync to Linear automatically, your Linear workspace must have Manage workspace labels set to All members (found under Linear’s Settings > Security). If that’s not enabled, you’ll need to create the labels manually in Linear.
3

Label tickets and generate docs

When a team member adds the @skills:add-docs label to a ticket like this:
ENG-215: Add POST /api/v2/webhooks endpoint — accepts a URL and event types, validates the URL is reachable, stores the subscription, and returns the webhook ID.
Devin automatically starts a session and follows your docs skill:
  • Reads the ticket — pulls the endpoint description, parameters, and any linked PRs
  • Finds the source code — locates the route handler, request validation schema, and response types
  • Generates documentation — creates a new page in docs/api/ following your existing format
  • Opens a PR — includes the new doc page and updated sidebar
This works well for batch operations too — multi-select tickets with Cmd+A, right-click, and add the @skills:add-docs label to generate docs for multiple endpoints in parallel.
With the Linear integration installed, Devin natively has access to Linear’s tools — so your skill can instruct Devin to update ticket labels or status based on the outcome. Since labels can trigger other automations, you can chain workflows — e.g., after docs are generated, a Docs Ready label could notify the tech writer for review.
4

Build more skills for your team

The same pattern works for any recurring task. Create a skill, sync it as a label, and your team can trigger it from any ticket. Here are some ideas:
  • @skills:write-tests — Add test coverage for the feature described in a ticket
  • @skills:refactor — Refactor code following your team’s conventions
  • @skills:security-audit — Review code for security vulnerabilities and open a PR with fixes
  • @skills:migrate — Run a standardized migration (dependency upgrade, API version bump)
You can also set up automations so Devin starts working without anyone applying a label at all. Go to Settings > Connections > Linear, scroll to Automations, click Add automation, and configure an automation that fires when tickets transition to a specific status or label.