pi-anthropic-auth: Skill for Claude Code

Shell traps

Load this skill before composing a non-trivial bash call. The zsh facts every session needs (no word-split of an unquoted parameter, =word expansion, $status read-only, an unquoted glob aborting) stay in AGENTS.md; this is the rest.

Command flags and state

rg -r is --replace, not --recursive; rg recurses by default, so drop the -r (Refs #47, #66, #74). Each bash call runs in a fresh shell — a variable set in one call is unset in the next. Chain producer and consumer in one call, or re-derive the value. Pass file tool paths repo-relative (src/x.ts), not hand-built absolute ones — a mistyped absolute path fails confusingly instead of fast, and trips pi-permission-system's external_directory gate when that extension is installed. The zsh echo decodes backslash escapes (\u2014 prints an em-dash; bash and dash print it literally), so it misreports a file's literal escape text; print bytes with print -r --, printf '%s\n', or sed -n.

Bodies with backticks

A gh issue comment / gh pr comment body containing backticks or fences belongs in a file passed with --body-file, whatever the quoting. Single quotes ship a \` literally, and double quotes need every ` escaped, where one miscount publishes mismatched code spans. A git commit body with quotes or backticks belongs in a file passed with -F <file>, written with Write — never -F - from a heredoc. A -m string corrupts one silently; the damage shows only in git log -1 --format=%B.

Pipelines

Do not pipe a long-output command into an early-exiting reader (head -1, sed -n '1p;q') under set -euo pipefail — the reader closes the pipe, the writer dies of SIGPIPE, and pipefail promotes the 141 into a script abort. It is a race that fires only once output exceeds one 4096-byte stdio buffer, so it survives for months and then fails always. Let the command do its own limiting: git for-each-ref --count=1, not git tag --list | head -1.