Personal dotfiles managed with GNU Stow. Each top-level directory is a stow package that mirrors the structure of $HOME. Running install.sh symlinks everything into place and safely backs up any pre-existing files that would conflict.

Run check_deps.sh to verify what is and isn't installed — it can also install missing tools automatically.

# 1. Clone the repo
git clone git@github.com:crueber/dotfiles.git ~/.dotfiles
cd ~/.dotfiles

# 2. (Optional) Check and install dependencies
./check_deps.sh
# or auto-install everything without prompts:
./check_deps.sh --yes

# 3. Stow all packages into $HOME
./install.sh

install.sh is safe to re-run at any time. It will never silently overwrite existing files — conflicts are renamed to <original>.bak.<timestamp> before stowing.

Each top-level directory is a stow package. The directory tree inside it mirrors $HOME, so stow knows exactly where to create symlinks:

dotfiles/
├── bin/
│   └── bin/          → ~/bin/
├── git/
│   ├── .gitconfig    → ~/.gitconfig
│   └── .gitignore    → ~/.gitignore
├── lsd/
│   └── .config/
│       └── lsd/      → ~/.config/lsd/
├── oh-my-posh/
│   └── .oh-my-posh/  → ~/.oh-my-posh/
├── tmux/
│   ├── .tmux.conf    → ~/.tmux.conf
│   └── .tmux/        → ~/.tmux/
└── zsh/
    ├── .zshrc        → ~/.zshrc
    └── .aliases      → ~/.aliases

Note on bin/bin/ double-nesting: Stow would normally symlink the entire bin/ package directory as ~/bin. The inner bin/bin/ nesting causes stow to instead create ~/bin/ as a real directory and symlink each script individually inside it. This is intentional — it keeps ~/bin/ as a real directory that can safely contain non-stow-managed files alongside the symlinked scripts.

The install script does the following:

1. Discovers all stow packages dynamically (any top-level directory that isn't .git, .github, node_modules, etc.)
2. Runs stow --dry-run to detect conflicts without making any changes
3. Parses the dry-run output to find exactly which files would conflict
4. Renames only those conflicting files to <path>.bak.<timestamp>
5. Runs stow -R (restow) to apply all packages

Backups are timestamped so re-runs never clobber previous backups. Symlinks that already point into the repo are skipped.

Checks for all required and recommended tools. Detects the available package manager (Homebrew, apt, pacman) and can install anything missing. Accepts --yes to skip confirmation prompts.

./check_deps.sh        # interactive
./check_deps.sh --yes  # auto-install all missing tools

• .zshrc — Initializes oh-my-posh with the blue-owl-custom theme, activates mise, sets EDITOR/VISUAL to nvim, configures PATH for ~/bin, LM Studio, and opencode.
• .aliases — Shell aliases: ls=lsd, vim=nvim, n=nvim, cat=bat, ll="ls -al", ..="cd ..", lg=lazygit

Local overrides: Create ~/.zshrc.local for machine-specific settings (tokens, private paths, etc.). It is sourced automatically if it exists and is excluded from git via .gitignore.

• .gitconfig — User info, push default (current), useful aliases (aa, ap, ci, co, st, rebase-origin), delta as pager/difftool/mergetool (dark mode default; switch to light via DELTA_FEATURES=+light), and a commit message template.
• .gitignore — Global ignores: .DS_Store, editor swap files, common Rails and macOS artifacts.

• .tmux.conf — Loads tpm, tmux-sensible, and tmux-themepack with the powerline/default/blue theme. Mouse support and tmux-256color terminal are enabled.
• .tmux/plugins/tpm/ — TPM is vendored directly in the repo so it's available immediately after stowing without a separate bootstrap step.

After stowing, install tmux plugins by pressing prefix + I inside a tmux session.

Four prompt themes are included. The active theme is set in .zshrc:

To switch themes, update the --config path in zsh/.zshrc.

• config.yaml — Enables color always, sets a custom color theme.
• colors.yml — 256-color palette for file type coloring.

Scripts symlinked into ~/bin/ and available on $PATH:

aaxclean-cli note: This binary is no longer vendored in the repo. Download the appropriate build for your platform from the aaxclean-cli releases page and place it in ~/bin/ manually.

1. Create a top-level directory named after the package (e.g., ssh/)
2. Inside it, recreate the path structure as it should appear under $HOME (e.g., ssh/.ssh/config)
3. Re-run ./install.sh — the new package is picked up automatically

Never commit secrets or machine-specific configuration. Use ~/.zshrc.local instead:

# ~/.zshrc.local  (not tracked in git)
export GH_TOKEN="your-token-here"
export SOME_API_KEY="..."

The .gitignore at the repo root excludes zsh/.zshrc.local and .zshrc.local to prevent accidental commits.