standup

A stand-up summary tool for software repositories. A stand-up is a short progress update; this one collects pull requests, reviews, commits, and code changes since the previous update.

In plain words
What is it for?
Use it to prepare a spoken or written daily update across configured repositories. It can cover authored or reviewed pull requests, merges, commits, and per-repository changes.
Why use it?
It removes the need to inspect each repository and pull request manually. It puts the user's own work first and groups activity into a concise update.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/ryanb/dotfiles/standup
Any agent
npx skills add ryanb/dotfiles --skill standup
Clone the repo
git clone --depth 1 https://github.com/ryanb/dotfiles

Made for: Claude Code, Codex.

Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,109 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00044 $0.03109
Opus 5 $0.00022 $0.01554
Sonnet 5 $0.00009 $0.00622
Haiku 4.5 $0.00004 $0.00311

Measured 2d ago against content hash 262fd23b7d7a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

standup scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (find-repos.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

claude/skills/standup/SKILL.md · 240 lines

How it starts

The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.

standup — Summarize work since last standup

Summarize work done in the user's configured repo directory since the last standup, grouped by category. The output is meant to be read aloud at a standup, so keep it concise.

Priority of the output — put the user's own work first:

  1. PRs the user created within the window (any state).
  2. Other PRs the user authored that had activity in the window (updates, new commits, state changes).
  3. Activity on other people's PRs (reviews, merges, comments).
  4. Local branches with a summary of the user's own commits (ignore commits by others).

Step 1: Load configuration

Read ~/.claude/standup.json. If the file does not exist, stop and instruct the user to create it with this shape:

{
  "base_path": "~/code/your-project-root",
  "default_branch": "main",
  "preferences": "Optional freeform instructions applied to the output."
}

Only base_path is required. Extract the values with jq:

config=~/.claude/standup.json
base_path=$(jq -r '.base_path // empty' "$config")
default_branch=$(jq -r '.default_branch // "main"' "$config")
preferences=$(jq -r '.preferences // empty' "$config")
# Expand a leading ~ in base_path
base_path="${base_path/#\~/$HOME}"

If base_path is empty, stop with an error.

Step 2: Determine the since date

Priority:

  1. If $ARGUMENTS is non-empty, use it verbatim as the since date.
  2. Else if ~/.claude/standup-last-timestamp exists, read its contents and use that as the since date. The file stores an ISO 8601 timestamp written by a previous run of this skill.
  3. Else default to 24 hours ago.

Store the chosen value in $since. Also compute a full ISO 8601 timestamp for gh search — GitHub search accepts >=YYYY-MM-DDTHH:MM:SSZ, and we want time-of-day precision so reruns in the same day don't re-list already-reported PRs.

# If $since is already an ISO timestamp (from the last-timestamp file), normalize to UTC Z form.
# Otherwise resolve the relative phrase via BSD date.
if [[ "$since" == ????-??-??T* ]]; then
  # e.g. 2026-04-13T11:11:39-0700 → 2026-04-13T18:11:39Z
  since_ts=$(date -j -u -f "%Y-%m-%dT%H:%M:%S%z" "$since" +%Y-%m-%dT%H:%M:%SZ)
else
  # Parse forms like "36 hours ago", "24 hours ago", "2 days ago", "yesterday",
  # "last friday", "past 36 hours" — normalize to BSD `date -v` adjustments.
  case "$since" in
    "yesterday")                  adj="-1d" ;;
    "last friday")                adj="-fri" ;;
    *"hour"*|*"hours"*)           n=$(echo "$since" | grep -oE '[0-9]+'); adj="-${n}H" ;;
    *"day"*|*"days"*)             n=$(echo "$since" | grep -oE '[0-9]+'); adj="-${n}d" ;;
    *"week"*|*"weeks"*)           n=$(echo "$since" | grep -oE '[0-9]+'); adj="-${n}w" ;;
    *)                            adj="-1d" ;;  # safe default
  esac
  since_ts=$(date -j -u -v"$adj" +%Y-%m-%dT%H:%M:%SZ)
fi

Read the full file on GitHub · 240 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 240 lines · 44 tokens per session scan A 262fd23b7d7a

Subscribe to this mod's changes

standup is a skill published in the GitHub repository ryanb/dotfiles (2,399 stars, last pushed 13d ago), licensed MIT. It adds 44 tokens to every session and 3,109 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens