dotfiles

Personal development environment for Linux and macOS, managed by mise. Rootless - nothing requires sudo.

Quick start

curl -fsSL https://raw.githubusercontent.com/acefei/dotfiles-mise/main/install.sh | sh

Project layout

dotfiles/
├── mise.toml               # Tools, env vars, and simple tasks
├── install.sh              # Fresh-machine bootstrap entry point
├── lib/
│   └── utils.sh            # Shared bash helpers (is_mac, download, …)
├── shell/
│   ├── dynamic_source_all  # Sources every shell/_* file at login
│   ├── _aliases
│   ├── _functions
│   ├── _fzf
│   ├── _git
│   ├── _prompt
│   └── _worktree
├── config/
│   ├── git/                # gitconfig, gitignore_global
│   ├── tmux/               # tmux.conf
│   └── vim/                # vimrc, plug_installer
├── agents/
│   ├── claude/             # settings.json, hooks/
│   └── vscode/             # settings.json, keybindings.json, extensions.txt
├── utility/                # Scripts symlinked to ~/.local/bin
├── templates/              # Cloud-init and Docker starter files
├── docs/                   # Reference docs (git aliases, fzf, worktrees)
└── .mise/tasks/            # Complex setup scripts (OS detection, loops, etc.)

Philosophy

Tools are anything mise can install and version-manage. Tasks are idempotent scripts that wire config files, generate completions, or do one-time setup steps that a package manager can't handle.

• Prefer a tool entry when: something has versioned releases and you want mise install / mise upgrade to manage it.
• Prefer a task when: setup is stateful (symlinking, building from source, writing config files) or needs OS-aware logic.
• Keep tasks idempotent — re-running mise run bootstrap on an existing machine should be safe.

Adding a tool

Add one line to mise.toml under [tools]:

[tools]
ripgrep = "latest"                    # built-in (mise registry)
"github:owner/repo" = "latest"        # any GitHub release binary

Then run mise install.

Adding a task

Simple one-liners go inline in mise.toml:

[tasks.setup-foo]
description = "Symlink foo config"
run = "ln -sf $MISE_PROJECT_ROOT/config/foo/foo.conf ~/.foo.conf"

Tasks with OS detection, loops, or multiple steps go in .mise/tasks/setup-foo (executable script, no extension). Add the task name to the depends list under [tasks.bootstrap].

Running individual tasks

mise run setup-git
mise run setup-agents
mise run bootstrap          # runs all tasks

AI agent settings

• Unified agents setup: the setup-agents task configures agent-related tooling in one stage.
• Claude Code: settings and hooks live in agents/claude/ and are symlinked to ~/.claude/ by setup-agents.
• VSCode: settings, keybindings, and extension list live in agents/vscode/ and are applied by setup-agents.
• skillfile: Install skillfile from cargo:skillfile (already in mise.toml) so it is built from source on the local machine. If Skillfile exists, setup-agents validates and installs the declared skills.