Skip to content
← All automations

Daily repo digest

Every weekday morning, what landed yesterday, which pull requests need you, and one next step.

Installs
0
Runs (30d)
0
Active builders
0
Trend
-100%

Uses

Tools: cli:git, composio:github

Triggers: Weekdays at 9:00 AM

Definition (YAML)

Download YAML
id: daily-digest
name: Daily repo digest
category: engineering
tagline: Every weekday morning, what landed yesterday, which pull requests need you, and one next step.
steps:
  - "Reads yesterday's commits (Friday through Sunday on Mondays)"
  - "Checks open pull requests, reviews and CI if GitHub is connected"
  - "Writes a short digest with one next step"
requires:
  - kind: cli
    id: git
    why: Reads yesterday's commits from the repository.
  - kind: composio
    id: github
    optional: true
    why: Adds open pull requests, review requests and CI status.
triggers:
  - kind: schedule
    cron: "0 9 * * 1-5"
install:
  agentMode: Ask
  speed: fast
  runMode: queued
  autoApproveTools: true
  maxRunMinutes: 15
replyStartsWith:
  - "## "
  - "**Landed**"
prompt: |
  Write the daily digest for the repository {{repo}} ({{target.path}}). Today is {{date}}.

  1. Commits: run `git log --since="yesterday 00:00" --until="today 00:00" --no-merges --pretty="%h %an %s"`. On Mondays use `--since="3 days ago"` to cover Friday through Sunday. If the folder is not a git repository, the Landed line is "Not a git repository" and you skip to the reply.
  2. Pull requests: if the `integrations` MCP server has GitHub connected, find this repo's open pull requests (find the tool with YOLOSESH_SEARCH_TOOLS, then call it with YOLOSESH_MULTI_EXECUTE_TOOL). Flag drafts, failing checks, requested reviews, and anything not updated for 7+ days. If GitHub is not connected, skip this part. Never start a connection flow yourself.
  3. Pick the single most useful next action for the maintainer.

  Reply with only this Markdown, under 20 lines, with nothing before or after it:

  ## {{repo}} · {{date}}

  **Landed** — one bullet per meaningful change (group trivial ones), with the short sha.

  **Needs attention** — pull requests with the reason, or "Nothing waiting". If GitHub is not connected, this line is exactly "Connect GitHub in Automations to include pull requests".

  **Next step** — one sentence.

  Read-only: do not edit files, push, comment, or change anything on GitHub.

Agent script

Write the daily digest for the repository {{repo}} ({{target.path}}). Today is {{date}}.

1. Commits: run `git log --since="yesterday 00:00" --until="today 00:00" --no-merges --pretty="%h %an %s"`. On Mondays use `--since="3 days ago"` to cover Friday through Sunday. If the folder is not a git repository, the Landed line is "Not a git repository" and you skip to the reply.
2. Pull requests: if the `integrations` MCP server has GitHub connected, find this repo's open pull requests (find the tool with YOLOSESH_SEARCH_TOOLS, then call it with YOLOSESH_MULTI_EXECUTE_TOOL). Flag drafts, failing checks, requested reviews, and anything not updated for 7+ days. If GitHub is not connected, skip this part. Never start a connection flow yourself.
3. Pick the single most useful next action for the maintainer.

Reply with only this Markdown, under 20 lines, with nothing before or after it:

## {{repo}} · {{date}}

**Landed** — one bullet per meaningful change (group trivial ones), with the short sha.

**Needs attention** — pull requests with the reason, or "Nothing waiting". If GitHub is not connected, this line is exactly "Connect GitHub in Automations to include pull requests".

**Next step** — one sentence.

Read-only: do not edit files, push, comment, or change anything on GitHub.