> ## Documentation Index
> Fetch the complete documentation index at: https://doc.entelligence.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Automation recipes

> Copy safe starter instructions for pull-request, sprint, team, security, budget, incident, and Slack-event automations.

These recipes default to analysis and delivery. Add writes only after a read-only version is stable.

## Weekly pull-request health

```text theme={null}
For TEAM and the previous calendar week, report:
- merged and open pull requests,
- median time to first review and merge,
- review comments and acceptance,
- the three longest-cycle pull requests with links.
State source gaps. Do not create or update anything.
```

## Monthly AI spend

```text theme={null}
For the current month, list projects over budget, near limit, and without a budget. Include spend, run rate, sessions, outcome mix, and untracked spend. Group by team and include source links.
```

## Reliability digest

```text theme={null}
For the last 24 hours, summarize new high-severity production detections, active recurring patterns, fixes ready, monitoring regressions, and open P0/P1 observability issues. Group by repository.
```

## Individual coaching report

```text theme={null}
For MEMBER and the last 14 days, summarize coding-agent tools, session trend, retry and context-health signals, and relevant skill suggestions. Frame this as enablement, not performance evaluation.
```

## Reactor: production alert context

Required keyword: `production alert`

```text theme={null}
Summarize the alert, find related active patterns and recent pull requests for the service, link evidence, and tag the mapped owner. Do not trigger a fix or create a ticket.
```

## Reactor: PR discussion summary

Required keyword: `PR:`

```text theme={null}
Summarize the decision, unresolved review concerns, linked ticket, and next owner. Post one concise reply with source links.
```

## Review every recipe

* Scope repositories, projects, teams, and time.
* Specify timezone.
* Ask for source links.
* State what to do when data is missing.
* State whether writes are forbidden.
* Choose one owner.
* Test one manual run.
* Verify no overlapping automation sends the same report.

## Next step

Create a [Pulse](/automations/pulse) or [Reactor](/automations/reactors).