env-checkup

env-checkup

A Claude Code skill that triple-checks, backs up, then optimizes your shell and developer dotfiles — safely.

• Mandatory backup before any edit — timestamped local backup + mackup backup (only if its storage is mounted). Removed orphans are moved to the backup, never deleted.
• Never prints secrets — token files, .npmrc auth lines, SSH keys, and history are redacted or checked by length, never echoed.
• Audits what actually bites you — duplicate compinit, completion fpath added after compinit, the ${ZDOTDIR} vs ${ZDOTDIR:-$HOME} cache bug, unexported NODE_OPTIONS, redundant nvm loads, PATH duplication, orphan rc files, stale .zcompdump*.
• Confirms before changing — an "orphan" is only flagged after grep proves it's sourced nowhere; a tool's config stays only if the tool exists. Intentional settings (e.g. strict-ssl=false) are flagged, not changed.
• Verifies — proves a fresh login+interactive shell loads clean, tools resolve, PATH has zero duplicates, and .gitconfig parses.

Works with zsh (primary), and adapts the same five steps to bash/fish.

Install

/plugin marketplace add th0mps0nty/organize-chrome-tabs
/plugin install env-checkup@th0mps0nty

Then just ask Claude Code for an "env checkup" (or run /env-checkup).

What it does

Step	Action
1. Inventory	Detect shell + load order, which dotfiles exist, backup tooling, tool availability
2. Triple-check	Read each rc file in load order and hunt the specific anti-patterns above
3. Back up	Timestamped local backup of every shell/git/npm dotfile before any edit
4. Optimize	Precise, context-anchored edits — never wholesale rewrites
5. Verify	Fresh zsh -lic proves a clean load, deduped PATH, resolving tools

A read-only audit helper lives at skills/env-checkup/scripts/audit.sh — run it standalone to inspect an environment without changing anything.

License

MIT © Tyler Thompson