Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
109 changes: 9 additions & 100 deletions features/automations.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -116,106 +116,15 @@ Choose which [coding agent](/features/coding-agents) runs your automation. Diffe

## Example Automations

### Auto-Generate PR Descriptions

Automatically create clear, well-formatted PR descriptions when PRs are opened.

**Trigger**: PR opened
**MCP Servers**: GitHub

```text
When a PR is opened, analyze the diff and generate a description:
1. Summarize what changed and why
2. List key modifications
3. Note any breaking changes
4. Add testing instructions
```

[Use this template →](https://tembo.io/for/pr-description-enhancement)

---

### Prioritize Sentry Errors

Get a daily report of the most impactful bugs, ranked by users affected.

**Trigger**: Daily at 8 AM
**MCP Servers**: Sentry, Slack, Linear

```text
Every morning:
1. Fetch errors from the last 24 hours
2. Rank by number of affected users
3. Post top 3 to #engineering-bugs
4. Create Linear tickets for each
```

[Use this template →](https://tembo.io/for/bug-triage)

---

### Automated PR Reviews

Get instant code reviews on every pull request.

**Trigger**: PR opened/updated
**MCP Servers**: GitHub

```text
Review this PR for:
- Bugs and logic errors
- Security vulnerabilities
- Performance issues
- Style guide compliance

Leave inline comments on specific lines.
Auto-approve if no issues found.
```

[Use this template →](https://tembo.io/for/pr-reviews)

---

### Security Vulnerability Scan

Scan your codebase daily for security issues.

**Trigger**: Daily
**MCP Servers**: GitHub, Linear

```text
Scan for:
- SQL injection
- XSS vulnerabilities
- Hardcoded secrets
- Authentication flaws

Create Linear tickets for each finding with severity ratings.
Generate fix PRs for critical issues.
```

[Use this template →](https://tembo.io/for/code-scanning)

---

### Enrich Linear Issues

Automatically add context to new Linear issues from your codebase, Slack, and docs.

**Trigger**: Linear issue created
**MCP Servers**: Linear, GitHub, Slack, Notion

```text
When a new issue is created:
1. Search codebase for relevant files
2. Find related Slack conversations
3. Pull in Notion documentation
4. Add a comment with implementation hints
```

[Use this template →](https://tembo.io/for/ticket-planning)

---
| Automation | Trigger | MCP Servers | What it does |
|------------|---------|-------------|--------------|
| [**PR Descriptions**](https://tembo.io/for/pr-description-enhancement) | PR opened | GitHub | Summarizes diff, lists changes, notes breaking changes, adds testing instructions |
| [**Bug Triage**](https://tembo.io/for/bug-triage) | Daily 8 AM | Sentry, Slack, Linear | Ranks errors by users affected, posts top 3 to Slack, creates Linear tickets |
| [**PR Reviews**](https://tembo.io/for/pr-reviews) | PR opened | GitHub | Reviews for bugs, security, performance, style; leaves inline comments |
| [**Security Scan**](https://tembo.io/for/code-scanning) | Daily | GitHub, Linear | Scans for SQL injection, XSS, secrets, auth flaws; creates tickets with severity |
| [**Issue Enrichment**](https://tembo.io/for/ticket-planning) | Linear issue created | Linear, GitHub, Slack, Notion | Searches codebase, finds Slack threads, pulls Notion docs, adds implementation hints |

Browse all templates at [tembo.io/for](https://tembo.io/for).

## Managing Automations

Expand Down