Skip to content

urmzd/dotfiles / dot_agents/skills/setup-devenv-with-chezmoi

setup-devenv-with-chezmoi

Verified

Chezmoi-specific dev environment helpers: writing pinned-version installer scripts (run_onchange_after_install-<tool>.sh.tmpl), maintaining the dot_envrc.project.example template, and the chezmoi diff/apply loop. Use when wiring a new pinned vendor installer (gcloud, aws-cli, Cortex) for the portfolio or scaffolding a chezmoi-tracked project envrc. Do NOT use for portable per-language version-manager or vanilla-direnv patterns; those live in setup-devenv.

Dev Env with Chezmoi

Personal-portfolio extensions to setup-devenv. This skill assumes a chezmoi-managed home directory and stays focused on the chezmoi-specific plumbing the portable skill deliberately omits.

When to Use

  • Adding a pinned-version installer for a tool that ships only via a vendor script (gcloud, aws-cli, Snowflake Cortex, etc.).
  • Updating the canonical dot_envrc.project.example template that new projects copy.
  • Standardizing how ~/.local/bin is wired up across projects.

If you're not on chezmoi, use setup-devenv directly. Substitute Brewfile / Nix / your own dotfile manager.

Pinned Installer Pattern

~/.local/share/chezmoi/run_onchange_after_install-<tool>.sh.tmpl

Skeleton:

#!/usr/bin/env bash
set -euo pipefail

<TOOL>_VERSION="<pin>"
INSTALL_DIR="$HOME/.local/share/<tool>/${<TOOL>_VERSION}"
BIN_PATH="${INSTALL_DIR}/<tool>"
BIN_LINK="$HOME/.local/bin/<tool>"

# Guard must test the actual install path, not a bin/ subdir, or the script
# re-downloads on every `chezmoi apply`.
if [ -x "${BIN_PATH}" ]; then
  exit 0
fi

mkdir -p "${INSTALL_DIR}"
curl -fsSL "<download-url>" -o "${BIN_PATH}"
chmod +x "${BIN_PATH}"

ln -sf "${BIN_PATH}" "${BIN_LINK}"

Conventions:

  • Pin the version at the top in ALL_CAPS. Bumping is a one-line diff.
  • Install to ~/.local/share/<tool>/<version>/. Versioned subdirs let you roll back without re-downloading.
  • Symlink into ~/.local/bin/<tool>. Keeps $PATH stable.
  • Mirror the structure of existing scripts like run_onchange_after_install-cloud-clis.sh.tmpl or run_onchange_after_install-cortex.sh.tmpl. Consistency makes the directory scannable.

Project envrc Template

The canonical project envrc lives at:

~/.local/share/chezmoi/dot_envrc.project.example

When a new project needs .envrc, copy this file into the project root, strip the per-language idioms that don't apply, and direnv allow. The portable patterns the file demonstrates (layout python, use fnm, PATH_add bin, dotenv, source_up) are documented in setup-devenv; this skill owns the file itself.

Apply Loop

After editing any of the above:

chezmoi diff
chezmoi apply

Run chezmoi diff first so you can confirm the rendered output matches expectations before overwriting the home directory.

Gotchas

  • Don't run installers eagerly. run_onchange_after_install-*.sh.tmpl re-runs only when its content changes. If the version pin doesn't change, chezmoi will skip it; this is intentional.
  • No secrets in templates. Use manage-secrets (1Password) or .env references. Templated installer scripts end up in git history.
  • Version subdirs over latest symlinks. A latest symlink obscures which version a script actually saw.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 321kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall