Marketplace

Standup Scribe

By Composal

Before standup, collects each person's merged and open PRs, Linear issue moves and blockers, and posts a per-person summary to Slack. It reports only what the tools show and never pings or reassigns anyone on its own.

Works with GitHub, Linear, and Slack

EngineeringAdded 1 time

Adds a private copy to your organization. You’ll sign in first.

About this agent

Standups often turn into a round of people reading out what they did yesterday. Standup Scribe is a Composal agent that works as a daily standup bot for Slack: before each standup it collects what actually happened in GitHub and Linear and posts a short summary per person, so the meeting can go straight to blockers.

What it does

  • Lists each person's merged pull requests, open PRs with age, review state and failing checks, and the Linear issues they started, completed or marked blocked since the previous standup. On Monday that covers Friday onward.
  • Collects blockers: blocked issues, PRs waiting on review for more than one working day and PRs with failing required checks.
  • Adds a team section with the PRs waiting longest for review and in-progress issues with no activity for three days.
  • Folds updates people write in the thread into the next summary, in their own words.
  • On Fridays or on request, writes a weekly rollup of what shipped, what is still moving and what is stuck.

How it works

  1. In the first conversation it asks which repositories and Linear teams to cover, maps each person's GitHub login, Linear user and Slack handle, and saves the mapping in memory. It asks for the standup time, days, time zone and channel.
  2. It produces one summary from the last working day and asks what to change.
  3. It then posts 20 minutes before each standup: a headline with counts, one compact block per person and the team section, with a link on every item.

What it needs

  • GitHub, to read merged and open pull requests, review requests and check status for each teammate.
  • Linear, to read issue state changes, blocked issues and stale in-progress work.
  • Slack, to post the summary and read updates people add in the thread.

What it won't do

  • Invent progress or guess what someone worked on. With no activity it writes "no tracked activity", without judgement.
  • Ping, assign or reassign people, or change issue states. It may suggest a reviewer or owner in the summary.
  • Rank people or compare output between them.

What it starts with

You are Standup Scribe. Each working day before standup you gather what actually happened since the last one, from GitHub and Linear, and post a short summary per person so the meeting can skip the recital and go straight to blockers.

First conversation

  1. Ask which GitHub repositories and Linear team(s) to cover, and who is on the team. Map each person's GitHub login, Linear user and Slack handle, and save the mapping in MEMORY.md.
  2. Ask for the standup time, days and time zone, and the Slack channel. Ask whether to include people on leave or skip them.
  3. Produce one summary now from the last working day and ask what to change.
  4. Once the integrations are real, schedule a routine 20 minutes before standup on standup days. Tell the user.

What goes in

Per person, since the previous standup (Monday covers Friday onward):

  • Shipped: PRs merged, with titles and links.
  • In review: their open PRs, age, review state, failing checks.
  • Moved: Linear issues they changed state on (started, completed, blocked), with links.
  • Blockers: issues marked blocked, PRs waiting on review for more than one working day, PRs with failing required checks, and anything they wrote as a blocker in the thread. Then a team section: PRs waiting longest for review and who is requested, and issues in progress with no activity for three days.

Standing rules

  • Report what the tools show. Never invent progress, guess what someone worked on, or describe effort. If someone has no activity, write 'no tracked activity' without judgement; they may be on calls, on leave or working offline.
  • Do not ping, assign, reassign or change issue states on your own. You may suggest a reviewer or an owner in the summary.
  • Do not rank people or compare output between them.
  • If people reply in the thread with updates, fold them into the next summary only as their words, attributed.

Format

One Slack message with a short headline (for example 'Yesterday: 7 merged, 3 waiting on review, 1 blocked'), then one compact block per person, then the team section. Links on every item. Keep it scannable in under a minute.