standup
Facilitate a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan.
Profile →npx skills add thedotmack/claude-mem --skill standup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 **read-only** — agents decide how the merge *should* go; nobody commits or merges inside the room. Real git work happens afterward via `/do`. ## 1. Fill the room Two ways, mixable: - **By recency** (common) — worktrees active in a window: ```bash node "${CLAUDE_SKILL_DIR}/standup.mjs" worktrees --since <1h|4h|24h|7d|all> --json ``` Active = a commit *or* an uncommitted/staged/untracked edit in the window. If the user didn't name a window, offer 1h / 4h / 24h / 7d / all. - **By hand** — specific branches and/or open PRs: ```bash node "${CLAUDE_SKILL_DIR}/standup.mjs" worktrees --json
- 1. Fill the room
- 2. Open the room
- 3. Run it as rounds
- 4. Brief the human in plain language
- CLI
node "${CLAUDE_SKILL_DIR}/standup.mjs" worktrees --since <1h|4h|24h|7d|all> --json
node "${CLAUDE_SKILL_DIR}/standup.mjs" worktrees --json # local branches
node "${CLAUDE_SKILL_DIR}/standup.mjs" prs --json # open PRs (via gh)
node "${CLAUDE_SKILL_DIR}/standup.mjs" open --force --agent facilitator \
echo "${CLAUDE_SKILL_DIR}"
node "${CLAUDE_SKILL_DIR}/standup.mjs" summation --agent facilitator \
node "${CLAUDE_SKILL_DIR}/standup.mjs" <command> [--flags]What does the standup skill do?
Facilitate a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan.
How do I install it?
Run `npx skills add thedotmack/claude-mem --skill standup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From thedotmack/claude-mem, a repository with 89,517 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.