Skip to content

Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows

skills(running-tend): fix the statusline cache-check recipe for Linux (#3825)

Worktrunk Bot350ad764ef4b
diff --git a/.claude/skills/running-tend/SKILL.md b/.claude/skills/running-tend/SKILL.md
index 7834702ac..9ca22410a 100644
--- a/.claude/skills/running-tend/SKILL.md
+++ b/.claude/skills/running-tend/SKILL.md
@@ -310,21 +310,30 @@ Discovery shortcut: a recent green CI run on `main` flags cargo-install drift di
## Weekly Maintenance: Statusline Cache-Check
Detect new in-process cache-miss duplicates introduced by recent changes by
-profiling a real `wt list statusline --claude-code` trace. The render runs on
-every Claude Code prompt redraw, so duplicate git subprocesses there compound
-into measurable fseventsd / IPC load.
+profiling a real `wt list statusline --format=claude-code` trace. The render
+runs on every Claude Code prompt redraw, so duplicate git subprocesses there
+compound into measurable fseventsd / IPC load.
```bash
-# Run from any worktree of this repo
-cat > /tmp/statusline-input.json <<'EOF'
-{"hook_event_name":"Status","workspace":{"current_dir":"REPLACE_WITH_CWD"},
- "model":{"display_name":"Opus"},"context_window":{"used_percentage":42.0}}
-EOF
-sed -i '' "s|REPLACE_WITH_CWD|$PWD|" /tmp/statusline-input.json
-
-cargo run --release -- -vv list statusline --claude-code \
+# Run from any worktree of this repo. `jq -n` builds the stdin JSON so the
+# recipe is portable (the weekly job runs on ubuntu-24.04, whose GNU sed
+# rejects BSD's `sed -i ''`) and so a path with a quote can't corrupt it.
+jq -n --arg cwd "$PWD" '{
+ hook_event_name: "Status",
+ workspace: {current_dir: $cwd},
+ model: {display_name: "Opus"},
+ context_window: {used_percentage: 42.0}
+}' > /tmp/statusline-input.json
+
+# Debug build on purpose. `tend-weekly` installs no `wt`, and its rust-cache
+# step is `save-if: false` under a key no workflow writes, so `--release`
+# means a cold optimized build of the whole dependency graph before the first
+# render. What this check reads — duplicate `(command, context)` pairs and the
+# subprocess count — is profile-independent; only the timing columns, which
+# this section doesn't triage, would be worth a release build.
+cargo run -- -vv list statusline --format=claude-code \
< /tmp/statusline-input.json > /dev/null
-cargo run --release -- config state logs profile --format=json | jq .cache
+cargo run -- config state logs profile --format=json | jq .cache
```
The `.cache` report flags commands invoked more than once with the same context.