standup

by thedotmack101k

Facilitate a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan.

Install

The skill file stays in the publisher's repository.

Paste the copied command in a terminal. It installs this SKILL.md into that agent.

npx skills add thedotmack/claude-mem --skill standup -a cursor -y

Download skill plugin/skills/standup/SKILL.md on GitHub

Related skills

View all

C
claude-memPersistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Cla
W
weekly-digestsGenerate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the p
W
what-theWhat the? Use when the user wants a plain-English breakdown of something technical — the who, what, where, why, and when.

Questions

How do I install standup?: Download plugin/skills/standup/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does standup live?: The publisher keeps it at https://github.com/thedotmack/claude-mem.
Which agents can use standup?: Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.

name: standup version: 1.0.0 description: Facilitate a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan. allowed-tools:

Bash
Read
Edit
Task
AskUserQuestion

standup — facilitate a group chat between branch-agents

You're the facilitator. Each of the user's git worktrees (and any PRs they pick) joins a shared markdown chat as its own agent, and the agents reconcile their scattered work into ONE consolidated worktree. You convene the room, run the conversation in rounds, and carry the outcome back — the reconciling happens in the chat, between the agents.

The room is one shared file (default ~/.claude-mem/STANDUP.md): YAML front matter holds the goal + prompt; the body is the transcript. Writes are atomically locked, so agents speak at once. It is — agents decide how the merge go; nobody commits or merges inside the room. Real git work happens afterward via .

command	what it does
`worktrees [--since 4h] [--json]`	worktrees newest-first; `--since N{m,h,d,w}` keeps those active in the window
`prs [--since 4h] [--json]`	open GitHub PRs (via `gh`) newest-first
`open --goal "…" --prompt "…" [--force]`	create the room (`--force` rotates an old one aside)
`join [--message "…"]`	add yourself + say Hello
`post --message "…" [--agree "…"]`	append a turn
`agree --deliverable "…"`	append an AGREE turn
`watch [--timeout SEC] [--interval SEC]`	block until someone else posts, print it (exit 2 on timeout)
`read [--tail N] [--since AGENT]`	print the chat (or only turns after AGENT's last)
`status`	participants + AGREEs + consensus check
`summation --text "…"`	write the SUMMATION, flip `status: agreed`

standup

Install

Related skills

Questions

standup — facilitate a group chat between branch-agents

1. Fill the room

2. Open the room

3. Run it as rounds

4. Brief the human in plain language

CLI