dotfiles: the uninstall list predates half of the repository
config files for zsh, bash, completions, gem, git, irb, rails
At a glance
- What is it?
- Ryan Bates's shell setup, one install script, two path shortcuts, and a Claude Code plugin directory with eleven skills and three JSON preference files. The most useful thing in it is the mismatch between the documented removal list and the editors and window managers the tree now carries.
- Who is it for?
- Use ryanb/dotfiles if you want one person's Zsh, git and editor setup as a starting point rather than a configurable framework, and if you are willing to read the files before running the installer over your own home directory. Three things to check.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly Vim Script, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- ryanb/dotfiles2,399 ★ · +1
| Repository | 2026-10-01 | 2026-11-15 |
|---|---|---|
| ryanb/dotfiles | 2.4k | 2.4k |
1 Stars in the last 45 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
One script copies the files and asks before it replaces them
Installation is three commands:
git clone [email protected]:ryanb/dotfiles ~/.dotfiles
cd ~/.dotfiles
./bin/installThe script's stated behaviour is to copy files over and to prompt before replacing when the files already exist, so an existing .zshrc turns the run into a series of questions rather than a silent overwrite. After it finishes, a new terminal window is required, because the shell reads its configuration at startup and the running shell will not pick up the new .zshrc. The README then says to feel free to customize the .zshrc file to match your preference, which is the intended relationship with the repository: install once, then edit the file in place inside the clone. The clone itself lives at ~/.dotfiles and stays there, and it is the clone that the uninstall step deletes at the end.
The clone address is an SSH URL with no https alternative
The install command clones [email protected]:ryanb/dotfiles, which is the SSH form and requires a working GitHub key before anything else happens. No https or archive alternative appears in the documented steps, so a machine without SSH configured fails at the first line rather than at a later step. The same choice shows up in the uninstall block, where the last two lines remove ~/.zshrc and then rm -rf the ~/.dotfiles directory, taking the clone with it. There is no package manager entry for this repository in the documentation, no formula and no manifest, which is consistent with a dotfiles tree whose install path is the clone plus a shell script. The bin directory is also where the uninstall guidance expects ~/.bin to come from, since that path is unlinked but never explained. One detail explains how the tree stays reviewable: the configuration files are committed without their leading dots. The root holds zshrc, gemrc, gitconfig, gitignore and irbrc as plain names, alongside directories such as vim/, so what lands in your home directory as .zshrc and .gemrc is produced by the install script rather than committed under that name.
c and h resolve against CODE_PATH and the first entry is the base
Two shortcuts do the path work. The c command points at the directory where the projects live, normally ~/code, and it completes: typing c railsca and pressing tab expands to the matching project directory. With no argument it opens fzf so you can fuzzy-find the directories instead. The h command behaves the same way against the home path, for example h doc and tab. Both read from an environment variable rather than a hardcoded path, and the example in the README is a colon separated list:
# in .zshrc
export CODE_PATH="$HOME/code:$HOME/code/railscasts-episodes"The instruction attached to it is that the first entry has to be the base one, which is what makes c expand relative to a single root while still searching the rest.
gw moves you into a worktree rather than switching branches
Two git behaviours are configured. The prompt carries the current branch name while the shell is inside a git repository, so the repository state is visible without running git status. The second is gw, which switches branches by way of fzf. The interesting case is what happens when the target branch is not checked out in the current working tree: if the branch is checked out in a worktree, gw changes directory into that worktree instead of failing or creating a new checkout. That is a deliberate accommodation for a workflow that keeps several worktrees open, and it also means gw has a side effect beyond git: it can move your shell out of the project you were in. Neither behaviour is configurable through a documented option, so both come from the .zshrc in the clone.
Eleven agent skills live in the same repository
The claude/ directory is a plugin, and .claude-plugin/ at the root is its manifest. Eleven skills are named: bisect, dependabot-prs, fix-all, gfix, interview, pr-feedback, pr-pending-feedback, rebase, review-queue, standup and walkthrough. Their descriptions range from running a test command through git bisect to find the first bad commit, to reviewing and merging open Dependabot pull requests, to ranking pull request reviews with dependency trees and filtered line counts, to summarising work since the last standup across configured repositories. Installation goes through a marketplace add and one install line per skill:
/plugin marketplace add ryanb/dotfiles
/plugin install bisect@ryanb-dotfiles
/plugin install gfix@ryanb-dotfiles
/plugin install review-queue@ryanb-dotfilesOnly three of the eleven are shown there, which means the plugin is larger than its own documented install example. What the skills do mechanically varies more than the names suggest. bisect runs a test command to find the first bad commit. fix-all runs bin/claude-review with --print and then fixes everything that was reported. gfix amends a commit further back in history using fixup plus auto-rebase. interview stress tests a plan by asking one numbered multiple choice question at a time. pr-feedback and pr-pending-feedback are the same idea for submitted and unsubmitted comments, and each address is handled in its own sub agent and its own commit. rebase is an interactive rebase workflow, and walkthrough reads pull request changes from the user's perspective rather than the diff's.
Three JSON files keyed by owner and repo carry instructions in prose
Three of the skills read a JSON file from the home directory, and all three use the same shape: an object whose keys are owner/repo and whose values are natural language instructions. dependabot-prs.json carries a per-repo instruction such as only handling pull requests with the javascript label. review-queue.json carries prioritisation rules, for example prioritising positive pull requests and excluding your own that are not yet approved. standup.json is structured differently, with a base_path, an optional default_branch and a preferences string; only base_path is required, and it points at the project root. The standup skill also writes its last-run timestamp to a separate file, ~/.claude/standup-last-timestamp, which is how a rerun shows only new work since the previous run. The three files live beside the plugin rather than inside it, so they survive switching the plugin off, and their values are read as instructions rather than as schema, which means a typo in a key silently does nothing instead of erroring.
The uninstall list stops at the classic dotfiles
The removal instructions are a block of unlink commands:
unlink ~/.bin
unlink ~/.gitignore
unlink ~/.gitconfig
unlink ~/.gemrc
unlink ~/.gvimrc
unlink ~/.irbrc
unlink ~/.vim
unlink ~/.vimrc
rm ~/.zshrc # careful here
rm -rf ~/.dotfilesEvery path there is a file from an earlier era of the repository. The tree now also holds aerospace/, ghostty/, kitty/, nvim/, wezterm/, plugins/, git-hooks/, tmux.conf and bin/, and none of those appear in the list. So a machine that adopted the Neovim config, a terminal emulator or the window manager configuration has to remove those by hand. The last two lines are the sharpest warning in the README: ~/.zshrc is removed rather than unlinked, with an inline note reading careful here, and the clone itself goes with rm -rf. The README also says to double check the contents before removing so you do not lose custom settings.
The README says Mac OS X and the language is Vim Script
The opening line describes config files to set up the Mac OS X command line the way the author likes it, using Zsh, and the repository description lists zsh, bash, completions, gem, git, irb and rails. The primary language recorded for the repository is Vim Script, which follows from the vim/ directory rather than from the shell setup most people come for. An older configuration that uses Oh My Zsh is kept on a separate branch of the same repository, so the main branch is plain Zsh and the framework based setup is one branch away. The text does not mention the editors, terminal emulators or window manager now in the tree, and it never mentions the git-hooks/ or plugins/ directories at all, so the documented surface is narrower than the committed one. The project has no GitHub releases, so the branch history is the only record of what changed. The last recorded push is dated 2026-09-30.
Editorial conclusion
Use ryanb/dotfiles if you want one person's Zsh, git and editor setup as a starting point rather than a configurable framework, and if you are willing to read the files before running the installer over your own home directory. Three things to check. The clone URL is an SSH address with no https alternative given, so have a key working first. The install script overwrites dotfiles in place after a prompt, and the README's own advice is to customize the .zshrc afterwards. And the documented uninstall list only covers the classic set, so if you adopt the nvim, kitty, wezterm, ghostty, aerospace, tmux or plugins directories, removing them is your job, not the script's.
Frequently asked questions
How do I install ryanb/dotfiles?
Clone the repository into ~/.dotfiles, change into that directory, and run ./bin/install. The script copies the files and prompts before replacing existing ones, and a new terminal window is needed afterwards to see the effects.
What does the c command do in ryanb/dotfiles?
It resolves to the code directory, normally ~/code, with tab completion. Without an argument it opens fzf to fuzzy-find the directories listed in CODE_PATH, whose first entry has to be the base directory. The h command does the same against the home path.
What does gw do in ryanb/dotfiles?
It switches git branches using fzf. If the branch is already checked out in a worktree, gw changes directory into that worktree instead of switching branches.
What skills does the claude directory in ryanb/dotfiles provide?
Eleven, among them bisect, dependabot-prs, fix-all, gfix, interview, pr-feedback, pr-pending-feedback, rebase, review-queue, standup and walkthrough. The install example shows adding the repository as a marketplace and installing three of them.
How do I uninstall ryanb/dotfiles?
Unlink ~/.bin, ~/.gitignore, ~/.gitconfig, ~/.gemrc, ~/.gvimrc, ~/.irbrc, ~/.vim and ~/.vimrc, then remove ~/.zshrc and the ~/.dotfiles directory. The README warns to check the files first so custom settings are not lost.
Does ryanb/dotfiles still use Oh My Zsh?
No. The main branch uses Zsh on its own, and an older version that uses Oh My Zsh is kept on a separate branch of the same repository.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/ryanb-dotfiles)Star history chart for your README
[](https://hysenlabs.com/projects/ryanb-dotfiles)Was this useful?