# Engineering

Source: https://routineos.org/use-cases/engineering

> The stale pull requests and red builds, every morning. A Claude routine for engineering teams, built from a real template. It starts report-only.

Use case: engineering

# Engineering routines for Claude: the stale pull requests and failing builds, every morning

One template writes a daily digest of open pull requests, bug issues and the latest build on each repository's default branch, and flags what has gone stale. It reads only and never merges, closes, comments, labels or reruns anything. It starts report-only. Free (MIT). Needs a paid Claude plan.

[Get started](https://routineos.org/#start)[See engineering digest](https://routineos.org/templates/engineering-digest)

engineering-digest: unpilotedexample scenario

The job

## The job: know what is waiting and what is red

Before the day starts, someone checks which pull requests are waiting for review, which issues are open and whether the main branch builds. Things go quiet in that list without anyone deciding to ignore them.

The scenario below is an example built only from what the template does.

An example week

## An example week with engineering digest

This is an example built from the real templates, not a customer story. It carries no results, numbers or quotes. Say a team lists three repositories and connects its code host.

1. **Sunday to Thursday, 21:00 UTC: the routine runs**For each repository it lists open pull requests, bug issues and the latest default-branch build. Draft pull requests are left out unless you turn them on.
2. **Code works out what is stale**A script computes age in days and flags anything not updated for seven days by default. Stale means time since the last update, not that work is blocked.
3. **You open the Desk**The digest shows what is open and what is stale, with up to five items in your Inbox by default. You act on them yourself, in your code host.
4. **You tune it**You open the Desk and keep, edit or drop what you see. The routine learns from those choices and suggests setting changes. Nothing applies until you say yes. For example, a repository that matches nothing for many runs in a row can be suggested for removal.

Source: template READMEs and catalog schedules in the [RoutineOS repository](https://github.com/devkindhq/routineos). Schedules are the template defaults, in UTC.

Templates

## The engineering template

 [

### Engineering digest

A daily digest of open pull requests, issues and failing builds, with the stale ones flagged.

unpilotedwatch
Open ](https://routineos.org/templates/engineering-digest)

**Needs**A code host connector with read access

**Default schedule**Sunday to Thursday, 21:00 UTC

**First run**Report-only

Maturity is from the catalog. This template has not had a real run yet, so read the first report-only run before you rely on it.

Safety

## What it never does

These come from the template prompts. They are rules the prompt forbids and the checks around it. They are not a promise about every possible run.

- The prompt forbids merging, closing, commenting, labelling or rerunning anything.
- The routine writes only its own run plan (runs, entities, inbox, views and columns).
- With no repositories set, the routine does nothing but say so.

**Heads up**A private repository's titles land in the store. Check that is acceptable before you add one. Treat a stale flag as a prompt to ask, not a judgement.

Next

## Where to go from here

Read the [engineering digest page](https://routineos.org/templates/engineering-digest) for install steps and settings. See the other teams on [all use cases](https://routineos.org/use-cases), read how [approvals](https://routineos.org/concepts/approvals) and [learning](https://routineos.org/concepts/learning) work, or check the [honest limits](https://routineos.org/honest-limits).

## Install engineering digest

It only reads. Run it report-only on one repository first and compare it with what you already know.

[Get started](https://routineos.org/#start)[Install engineering digest](https://routineos.org/templates/engineering-digest)