# Example automations

> Recipes to adapt for fixing failing CI checks, issue triage, a /fix command, and a daily summary email.

Each recipe lists the settings and sample **Instructions**. Change the text to fit your team, then [create the automation](/automations/create/). For a weekly security scan, turn on the **Weekly Security Scanner** in **Automations**.

## Fix failing CI checks

* **Trigger:** Pull Request / Check Failure, with **Job Name** equals `test`
* **Capabilities:** Push commit, Post Comment
* **Scope:** Selected repositories

Rerunning your tests before devlo pushes needs Startup or higher.

```text
A check failed on this pull request. Find the cause in the code, fix it, and push a commit. Then comment with what you changed. If you can't fix it, explain why.
```

## Triage new issues

* **Trigger:** Issue / New Issue
* **Capabilities:** Update Labels, Assign Issue, Post Comment
* **Scope:** All repositories

```text
Read the issue. Add the labels that fit (bug, feature, question). Assign the person who owns the affected area. Post a short comment asking for missing details.
```

## A `/fix` command

* **Trigger:** Pull Request / New Comment, with **Comment Body** contains `/fix`
* **Capabilities:** Push commit, Post Comment
* **Scope:** All repositories

```text
Read the comment that triggered you and fix what it asks for on this pull request's branch. Push one commit and keep the change small. Then reply with what you changed, or why you couldn't.
```

## Daily repository summary by email Paid plans

* **Trigger:** Schedule / Daily
* **Capabilities:** Send Email, with your address as the recipient
* **Scope:** Selected repositories, with one repository

Each repository in scope sends its own email.

```text
Summarize what merged, what is waiting for review, and what looks stuck in the last day. Keep it under 200 words.
```

## Related

* [Create and manage automations](/automations/create/)
* [Triggers and capabilities](/automations/triggers/)