git:20260914.f35d073 to git:20260923.6772416

---

name: standup

description: Brief on concurrent sessions — who else is working, in which repos, on which files, and what landed underneath you. Use when a commit appears that you did not make, before touching a shared file, or when orienting mid-task in a busy workspace.

allowed-tools:

- Bash

- Read

---

# Standup

`/focus` answers *what has happened in this project*. `/standup` answers *who

else is in it with me right now* — the peer view.

Every changelog event already carries `session_id`, `project`, `cwd` and a

summary naming the file or the commit, so this needs no new capture. It groups

what the hooks wrote by session instead of by project.

Before running, resolve `ROOT` to the Session Cartographer plugin root. Prefer

`CARTOGRAPHER_ROOT`, then `CLAUDE_PLUGIN_ROOT` or `PLUGIN_ROOT`. Otherwise

derive it from this skill's base directory (`../..` from `skills/standup`), with

the conventional checkout as a legacy fallback.

## The roster

```bash

node "$ROOT/scripts/cartographer-standup.js" --since 6h

```

event count, and its last commits (subjects recovered from git when the corpus

Scope it when the workspace is loud:

```bash

node "$ROOT/scripts/cartographer-standup.js" --project psychodeli-webgl-port --since 12h

```

## The part that matters

Read **CONTENTION** first; the roster is ambient. Two sessions awake is normal

and ignorable. Two sessions editing the same file is the thing that quietly

costs an hour, and it is the only line in the output that should change what you

do next.

- **Project contention** is the weak signal — expected in a repo under active

work. Note it, do not act on it.

- **File contention** is the strong signal. Before you edit a file listed there,

re-read it from disk rather than trusting anything you read earlier in the

Three things shape that list:

- **Workspace-root and worktree directory *names*** are filtered out of the

*project* line via `scripts/non-projects.js` — five sessions "sharing" `dev`

is the filesystem, not a collision. That filter never touches the *file* list:

a file's identity is its path, and two sessions running from the workspace

root collide on a file just as hard as two in a named repo.

- **A worktree edit and a main-checkout edit of one repo file are one file.**

## What it could not count

A silent miss and a clean workspace print the same thing, so the footer says

what fell out:

```

NOT COUNTED — 187 edit candidates did not resolve to a file on disk

(mostly the hook's non-paths; a since-deleted file also lands here);

2 events carry no resolvable session id and were counted, not grouped.

```

The edit hook reads shell source text and is loose by construction — roughly

56% of what it emits is not a path (`r.max`, `n.name`), which is expected. But a

real file deleted or renamed after the edit lands in the same bucket, and its

collision is simply absent from the list above. A large count next to a

suspiciously empty contention section is worth a second look.

Sentinel session ids (`unknown`, `""`) are counted here and never grouped: they

are truthy and equal to each other, so keying on them would fuse every

unattributed event — across providers — into one phantom session that appears to

collide with everybody.

## Attributing a commit you did not make

When a sha shows up under you — the common trigger for this skill — name its

session directly:

```bash

node "$ROOT/scripts/cartographer-standup.js" --commit c61e0e83 --since 24h

```

Prints the owning session, project, timestamp, files, and how many commits that

subject. A miss means the window is too short (`--since 3d`) or the commit

predates hook coverage — say which, do not guess at authorship.

## Reporting it

Lead with the collision, not the census. Andy runs 3-5 concurrent sessions by

design; a list of them is not news. Useful:

> `a1986975` landed `c61e0e83` (jukebox chip colours) 50m ago in the same repo.

> No file overlap with your work — `311a6cf7` and `7ca82aba` are both in

> `docs/TUNING.md` though.

Not useful: "there are 9 active sessions."

When a peer session is worth the operator's attention, hand over its Memory

Desk link rather than its id: `http://127.0.0.1:2527/memory?session=<id>`

opens that thread (span, edited files, observations, resume command), and

`&file=<url-encoded abs path>&review=changes` opens the contested file on that

session's bounded diff. The full permalink grammar is in the `/carto` skill

under "Deep links into Memory". Check the host answers 200 first; a link to a

stopped Explorer is worse than an id.

Never claim a session is *currently* running. The log shows last activity, not

liveness — `●` means it was active recently, which is a different claim. Say

"active 6m ago," not "is running."

## Flags

| flag | default | |

|---|---|---|

| `--since` | `6h` | window; `30m`, `12h`, `3d` |

| `--commit` | — | attribute a sha or subject substring to its session |

| `--live` | `20m` | idle threshold for the `●` marker |

| `--me` | inferred | override self-identification |

| `--all` | off | keep your own session in the peer roster |

Read-only. Writes nothing to the changelog and emits no retrieval telemetry.