Skip to content

Merged changes digest

Reads every pull request merged since the last run and writes a short digest of what changed. Each change is sorted by who it matters to and how big it is.

EngineeringWorks with Claude Code · OpenAI Agents SDK+1Community example
Build your promptSee requirements

What it does

  • Lists pull requests merged since the last digest
  • Sorts each by audience, size and kind of change
  • Leaves out minor changes and notes why
  • Writes the digest with a table of what made it in

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Publishing the digest

You decide what happens next.

More about this workflow

This setup is for developers and small engineering teams who want fewer chores. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it lists pull requests merged since the last digest. Next, it sorts each by audience, size and kind of change. Then it leaves out minor changes and notes why. Finally, it writes the digest with a table of what made it in. It works with your git host and docs site, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before publishing the digest, and says plainly if a step cannot be undone.

“RISE Changes writes a weekly digest of what merged, routed and composed by Claude”
SyberLabs SyberLabs on GitHub · Oct 15, 2026
Before you startGit host · Docs site accessScoped permissionsClaude Code or OpenAI Agents SDK
Explore required tools and model recommendations

Tools and access

  • GitHub

    Handles the git host part of this job. Grant a fine-grained token, read code and write comments.

    API required: Yes. Needs a GitHub App or a fine-grained personal access token scoped to the repos it needs.

    Sign up: Create a GitHub account

  • Docs site

    Handles the docs site part of this job. Grant draft or branch access, not publish.

    API required: Optional. Your docs repo or CMS. Most agents work through a branch or draft.

    No sign-up needed

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Claude Opus 5.5

Its maker points to it for long running coding work.

$4 per million input tokens, $20 per million output tokens.

Anthropic docs as of October 11, 2026

Cheaper backup

Claude Sonnet 5.5

Half the price per token and still strong for reviews and docs.

$2 per million input tokens, $10 per million output tokens.

Anthropic docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

e.g. team, customers

e.g. twice a week

2Your prompt

4 of 4 still empty
Fill these in before you run it: [YOUR REPO] [WHO READS IT: e.g. team, customers] [HOW OFTEN: e.g. twice a week] [WHAT TO LEAVE OUT] You are the Merged changes digest agent. Reads every pull request merged since the last run and writes a short digest of what changed. Each change is sorted by who it matters to and how big it is. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Lists pull requests merged since the last digest - Sorts each by audience, size and kind of change - Leaves out minor changes and notes why - Writes the digest with a table of what made it in What you must never do without a yes from a person: - Publishing the digest Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, OpenAI Agents SDK, LangGraph

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect GitHub with its own login, not yours. Grant a fine-grained token, read code and write comments.
  2. 2Set up Docs site. Keep it to draft or branch access, not publish.
  3. 3Paste the prompt where your harness takes instructions. See the note under the Copy button.
  4. 4Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  5. 5Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval27 / 30

Waits for a yes on: publishing the digest.

Undo and logs17 / 20

Leaves drafts you can throw away, with a record of what it made.

Scope18 / 20

Runs on its own login across 2 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Human approval: Add a second named stop next to "publishing the digest", so every step that leaves your hands waits for a yes, and have the confirm say plainly what cannot be undone +3
  • Scope: Run it on one tool only, with its own login that can see just what this job needs +2

Do all of these to reach 91, up from 80.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Merged changes digest](https://trustcase.dev/badge/merged-changes-digest.svg)](https://trustcase.dev/use-cases/merged-changes-digest)
HTML
<a href="https://trustcase.dev/use-cases/merged-changes-digest"><img src="https://trustcase.dev/badge/merged-changes-digest.svg" alt="Trustcase trust score for Merged changes digest" height="20"></a>

More engineering workflows

  • Morning QA report

    Runs a set of read-only checks on your codebase each morning and files one report issue. It starts as an observer and only gets more power when you grant it.

  • Upstream blocker recheck

    Once a month, re-tests the upstream bugs and missing releases your work is waiting on. Tells you which ones have cleared.

  • Daily public exploit digest

    Each day it checks public exploit sources for high severity flaws that just got working exploit code. It keeps one running monthly list so you know what to patch first.

  • Safe dependency update pull requests

    Finds outdated packages on a schedule, applies only small updates that pass your tests, and opens a pull request. Major updates are listed for a person.