edit-statusline

Files (all in scripts/, i.e. ~/my-skills/skills/edit-statusline/scripts/):

statusline-command.sh writes the raw payload of every redraw (of any session) to ~/.claude/statusline-last-input.json. That file is "the current payload". It is raw: never commit it, never paste it whole into a public place.

Workflow

1. Compare.

   python3 ~/.claude/skills/edit-statusline/scripts/compare.py

   It prints added / removed / type-changed key paths, value-dependent differences (a null on one side — not a schema change), and the paths the script reads that are absent now. Keys marked (situational) appear only in some situations (git repo, worktree, agent, vim, PR); their absence proves nothing. If statusline-last-input.json is missing or old, any redraw of any session rewrites it — just run the compare again.

2. Decide with the user. Report the differences (a short table: key, example, now). For each new key, say what it holds and whether it would be useful on the status line; for each key the script reads that is gone, say what goes blank. Propose concrete changes, and let the user decide whether to edit at all.
3. No edit → stop here. Leave example.json as it is, even if it differs from the current payload. Do not commit anything.
4. Edit → change both files.
   • Edit scripts/statusline-command.sh. Keep its header comment in sync (the "Line 2:" layout line and the notes).

   • Regenerate the baseline:

     cd ~/my-skills/skills/edit-statusline/scripts
     python3 redact.py > example.json

     redact.py replaces every id, path, session name and repo field with "..." and prints the strings it kept on stderr. Read that list: if a new field holds something personal (a name, a path, an id, a URL, a token), redact it by hand in example.json and add its key to KEYS in redact.py.

   • Test the script on the current payload without touching the real log:

     cd ~/my-skills/skills/edit-statusline/scripts
     STATUSLINE_USAGE_LOG=/tmp/sl-test.log STATUSLINE_LAST_INPUT=/tmp/sl-test.json \
       bash statusline-command.sh < ~/.claude/statusline-last-input.json | cat -v

     (Use the session scratchpad instead of /tmp when one is given.)

5. User checks the diff. Show git -C ~/my-skills diff (both files) and wait for the user's OK.
6. Commit ~/my-skills with the /commit workflow (no version bump).

Rules

• ~/.claude/statusline-usage.log keeps 5 columns (<epoch> <five%> <week%> <five_resets_at> <week_resets_at>, - if absent). The check-usage skill parses it by position. Changing the format means changing skills/check-usage/scripts/check-usage.py in the same commit.
• All payload fields are read in the single jq call (one process per redraw). Add new fields there; keep .workspace.current_dir last (free text).