# AI for Developers: 14 Workflows Source: https://maito.app/workflows/team/engineering 14 AI workflows for engineering teams, like turn a ticket into a tested pull request, review a teammate's pull request, write the changelog. Each shows the steps, an example and how to set it up. 14 workflows. Tickets to tested pull requests, first-pass reviews, changelogs, postmortems and dependency upgrades. Work your team keeps putting off. [Put Maito to work](https://maito.app/login?returnTo=%2Fworkflows%2Fteam%2Fengineering)[Book a demo](mailto:support@maito.app?subject=Maito%20demo) $149/month per workspace · Unlimited people · AI usage billed by your provider 69% of developers lose eight or more hours a week to inefficiencies. [Atlassian, State of Developer Experience 2024](https://www.atlassian.com/blog/developer/developer-experience-report-2024) ## All engineering workflows. 14 workflows - [Start here Turn a ticket into a tested pull request Hand over a well-scoped ticket and get back a pull request with tests. Engineering · When you ask Works with Linear, Jira.](https://maito.app/workflows/turn-a-ticket-into-a-tested-pull-request) - [Start here Review a teammate's pull request Get a first review that catches bugs and missed cases before a person looks. Engineering · When something happens Works with Slack, Email.](https://maito.app/workflows/review-a-teammates-pull-request) - [Start here Write the changelog Twice a week, turn merged pull requests into a changelog people can read. Engineering · On a schedule Works with Slack, Email.](https://maito.app/workflows/write-the-changelog) - [Check a change for security problems Look at a change for injection, leaked secrets and missing permission checks. Engineering · When you ask Works with Slack, Email.](https://maito.app/workflows/check-a-change-for-security-problems) - [Nudge stale pull requests Pull requests waiting too long get a polite reminder to the right reviewer. Engineering · On a schedule Works with Slack, Email.](https://maito.app/workflows/nudge-stale-pull-requests) - [File a bug from a Slack thread When a bug comes up in chat, mention Maito and it gets filed once, with details and no duplicates. Engineering · When you ask Works with Linear, Jira.](https://maito.app/workflows/file-a-bug-from-a-slack-thread) - [Draft the incident postmortem Turn the incident channel and logs into a postmortem draft. Engineering · When you ask Works with Datadog, Sentry.](https://maito.app/workflows/draft-the-incident-postmortem) - [Investigate an error spike When errors jump, get a first look at the cause before anyone opens a laptop. Engineering · When something happens Works with Datadog, Sentry.](https://maito.app/workflows/investigate-an-error-spike) - [Update docs when the code changes When an API or setting changes, the docs get a matching update. Engineering · When something happens Works with Notion, Confluence.](https://maito.app/workflows/update-docs-when-the-code-changes) - [Upgrade a dependency Bump a library, fix what breaks and open a pull request. Engineering · When you ask Works with Slack, Email.](https://maito.app/workflows/upgrade-a-dependency) - [Answer "where is this in the code?" New engineers and other teams get answers about the codebase in chat. Engineering · When you ask Works with Slack, Email.](https://maito.app/workflows/answer-where-is-this-in-the-code) - [Weekly engineering digest What shipped, what's stuck and what broke, in one message for the team. Engineering · On a schedule Works with Linear, Jira.](https://maito.app/workflows/weekly-engineering-digest) - [Clean up flaky tests Find tests that fail at random and fix or quarantine them. Engineering · On a schedule Works with Slack, Email.](https://maito.app/workflows/clean-up-flaky-tests) - [Write a technical design draft Turn a feature idea into a design doc that fits how the code works today. Engineering · When you ask Works with Slack, Email.](https://maito.app/workflows/write-a-technical-design-draft) [See how engineering teams use Maito](https://maito.app/use-cases/engineering) ## Where AI helps an engineering team. Maito works in your repositories. It turns a ticket into a tested pull request, reviews a teammate's pull request, checks a change for security problems and upgrades a dependency on a branch. Around the code, it files a bug from a Slack thread, drafts the incident postmortem from the channel and logs, investigates an error spike, and writes the changelog on a schedule. Engineers keep every decision that ships. An engineer reviews and merges each pull request, the author decides what to fix from a review, and an engineer decides on a rollback when an error spike shows up. A security lead signs off where needed. Maito does not merge code, and it does not change production. Start with a small ticket you would hand to a new hire. Connect your repository and issue tracker, then mention @Maito in the ticket's Slack thread and ask for a pull request. Read the diff as you would any other. Once you trust the output, set up the weekly engineering digest or the stale pull request nudge as a Loop. ## Questions. ### Does it merge code? No. It opens a pull request with tests. Your team reviews and merges. ### Where does it run the code? Each coding task gets its own sandbox, branch and checkout, so several can run at once. ### How long does it take to set up? Minutes for the workspace: create it, connect your AI provider and connect Slack. Each workflow then takes one request to your agent, plus signing in to any tool it needs. ### Do we need a developer? No. You set up each workflow by asking your agent in plain words. A repository is only needed for coding work. ### What does it cost? $149 per workspace per month, with unlimited people and $20 in cloud credits each month. Your AI provider bills its usage separately. ## Put your AI teammate to work. Set it up in minutes. Start with one workflow, and let it earn the next one. [Put Maito to work](https://maito.app/login?returnTo=%2Fworkflows%2Fteam%2Fengineering)[Book a demo](mailto:support@maito.app?subject=Maito%20demo)