Software Development Skills

Adding and editing YAML/TOML data files under home/.chezmoidata/ that templates consume — aliases, packages, themes, ghostty config, tmux plugins, authorizedkeys. Triggers on ".chezmoidata", "aliases.yaml", "packages.yaml", "themes.yaml", "add a brew package", "add an alias to dotfiles", "template data", "update homebrew bundle".

Managing third-party content fetched via Chezmoi externals — home/.chezmoiexternals/.toml.tmpl files for zsh plugins, fish plugins, tmux plugins, ghostty themes. Pinning by commit SHA so Renovate can update them. Triggers on "chezmoi external", "chezmoiexternal", "zsh-autosuggestions", "tmux plugin", "fish plugin", "pin to commit", "Renovate dotfile", "third-party content".

Authoring runonce and runonchange scripts under home/.chezmoiscripts/ — idempotency, strict mode, DEBUG awareness, template-data inputs, and how Chezmoi decides when to re-run them. Triggers on "runonchange", "runonce", "chezmoi script", ".chezmoiscripts", "install packages script", "post-apply script", "trigger on apply".

Writing and debugging Chezmoi .tmpl files using Go text/template — lookPath, stat, joinPath, OS branching, the .chezmoi namespace, and template data from .chezmoidata. Triggers on "chezmoi template", ".tmpl", "Go template", "lookPath", "promptStringOnce", ".chezmoi.os", "template render error", "conditional dotfile content", "branch by OS".

Day-to-day Chezmoi loop for a dotfiles repo — edit only in the source tree, preview with chezmoi diff, apply targeted or full, validate with chezmoi status. Covers partial apply, troubleshooting drift, and recovering from accidental edits in $HOME. Triggers on "chezmoi diff", "chezmoi apply", "chezmoi status", "dotfile change", "apply my dotfiles", "what changed in my dotfiles", "drift", "chezmoi destination is different".

Audit TypeScript code for quality, complexity, coupling, and clean code violations. Use when reviewing code quality, checking for anti-patterns, assessing maintainability, or before major refactoring.

Review gate owned by code-reviewer; security-engineer leads for sensitive changes (auth, payments, secrets, permissions). Covers what to check, a severity taxonomy (blocking / should-fix / nit), a review checklist, how to give actionable feedback, and when to request changes vs. approve. Use when someone says "review this", "code review", "is this ready to merge", "check this PR", "look at my diff", "LGTM?", or "give me feedback on this code".

Universal dependency installer that auto-detects the project's package manager (uv, bun, npm, yarn, pnpm, cargo, go, bundler, brew) and runs the correct install command for dev, global, or project-local installs. Use when the user wants to install dependencies without worrying which package manager the project uses, add a package as a dev dependency, install globally, sync the lockfile, or when they mention "install dependencies", "add package", or "run the right package manager here".

Fast file finding using fd command-line tool with smart defaults, gitignore awareness, and parallel execution. Use when searching for files by name, extension, or pattern across directories.

Guides fnox secrets management configuration via fnox.toml — file structure, secrets definition, profiles, hierarchical config, mise integration, import/export, and sync. Always use fnox as a mise integration, never as standalone shell integration. Triggers on: "set up fnox", "fnox.toml", "configure fnox", "fnox profiles", "fnox secrets", "mise fnox", "migrate to fnox", "fnox sync", "fnox import", "fnox export".

Guides fnox provider selection and setup — age encryption, AWS (Parameter Store and Secrets Manager), 1Password, Bitwarden, GCP, Azure, Doppler, Vault, and local options. Triggers on: "set up fnox provider", "fnox age", "fnox aws", "fnox 1password", "which fnox provider", "configure fnox provider", "fnox encryption", "add provider to fnox".

Security best practices for fnox — key rotation, gitignore rules, CI/CD secret handling, access control, missing-secret enforcement, and avoiding common mistakes. Triggers on: "fnox security", "rotate fnox keys", "fnox gitignore", "fnox ci secrets", "fnox key rotation", "fnox access control", "fnox reencrypt", "secure fnox setup", "fnox best practices".

Monitor GitHub Actions workflow runs with blocking watch commands instead of polling loops or timeouts. Use when the user wants to watch a workflow run until it completes, wait for CI after a push, trigger a workflow and follow its progress, diagnose a failed run with gh run view --log-failed, or find the latest in-progress runs.

Create PRs via GitHub API without local git operations. Use when you want to submit file changes as a PR without committing locally — for quick fixes, typos, config updates, or when you want a clean workflow that bypasses local git state entirely.

Git branch naming conventions for consistent, traceable branches. Use when creating new branches, discussing branch naming standards, or setting up repository conventions. Covers type prefixes (feat, fix, chore), issue linking, and kebab-case formatting.

Branch management, pull request workflows, and GitHub integration. Main-branch development pattern (push main to remote feature branches), modern Git commands (switch, restore), and GitHub MCP tools. Use when user mentions creating branches, opening PRs, git switch, git restore, feature branches, pull requests, or GitHub PR workflows. For naming conventions see git-branch-naming, for rebase patterns see git-rebase-patterns.

Git commit trailer conventions and patterns. Use when composing commit messages that need BREAKING CHANGE, Release-As, Co-authored-by, Signed-off-by, or other trailer lines. Covers release-please trailers for version control, attribution trailers, and git interpret-trailers for parsing and adding trailers programmatically.

Commit message conventions, staging practices, and commit best practices. Covers conventional commits, explicit staging workflow, logical change grouping, humble fact-based communication style, and automatic issue detection. Use when user mentions committing changes, writing commit messages, git add, git commit, staging files, or conventional commit format.

Resolve merge conflicts. Use when a merge or rebase has conflicts, a PR can't merge, "fix conflicts" appears, or you need to reconcile diverged branches. Handles file-by-file resolution with modern git tooling.

Detect whether another Claude agent is working in the same repo clone before running destructive git operations (stash, reset, checkout --). Use when starting a session in a non-worktree checkout, or before any "clean up the working tree" action that could wipe a coworker's in-flight changes.

Analyze git commit history to derive undocumented rules, PRDs, ADRs, and PRPs. Use when the user asks to find documentation gaps, detect architectural decisions that were never recorded, derive coding conventions from commit patterns, or generate skeleton rules/PRDs/ADRs/PRPs from existing git history.

Analyze and fix failing PR checks. Use when the user asks to fix the PR, resolve failing CI checks, diagnose red GitHub Actions runs, auto-fix lint/type/test failures on a pull request, or reproduce CI errors locally before pushing corrections.

Fork management and upstream synchronization. Use when working with forked repositories, syncing fork with upstream, managing divergence between fork and upstream, or preparing commits for upstream contribution. Covers remote architecture, divergence detection, sync strategies, and cross-fork PRs. For creating upstream PRs, see git-upstream-pr.

Process GitHub issues end-to-end with TDD, interactive selection, conflict detection, and parallel work support. Use when the user asks to work on an issue, fix issue N, pick issues to tackle, batch-process several issues in parallel, or spin up PRs from a prioritized issue list.