Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows
skills(writing-user-outputs): document the stderr half of the anstream macro rule (#3797)
Worktrunk Bot91b7beff57f1
diff --git a/.claude/skills/writing-user-outputs/SKILL.md b/.claude/skills/writing-user-outputs/SKILL.mdindex 1bae7f498..067cc6f65 100644--- a/.claude/skills/writing-user-outputs/SKILL.md+++ b/.claude/skills/writing-user-outputs/SKILL.md@@ -60,6 +60,20 @@ panics on the `BrokenPipe` write error, anstream's drops it. `wt … | head`closes the pipe, so command code imports the `worktrunk::styling` one and no`std::println!` is left in `src/`.+The stderr macros carry the same rule for a different consequence: anstream's+`eprint!` / `eprintln!` strip ANSI when stderr isn't a terminal, std's keep it,+so a file importing one but not the other writes escapes on one line of a+message block and not the next under `wt … 2>log`. `eprint!` is the half that+slips — it has no newline, so it gets reached for mid-block in a file that+imported only `eprintln`. Every bare `eprint!` / `eprintln!` under `src/` must+resolve to anstream's: import it, or qualify the call as+`styling::eprintln!(…)`. `check_stderr_macros_come_from_styling` in+`tests/integration_tests/output_system_guard.rs` holds that statically, since+no snapshot can — the suite forces `CLICOLOR_FORCE=1`, so both printers emit+color and a snapshot agrees whichever macro is in scope. Its+`STD_STDERR_ALLOWED_PATHS` exempts whole files, not calls, so an entry is only+right where std's macro is right throughout.+**Output whose ANSI is already decided** declares that once at the top of thecommand with `worktrunk::styling::ColorChoice::Always.write_global()` and thenprints through the same anstream macros — the statusline a shell prompt or