Dotfiles

A collection of configuration files for the tools/programs I use in my day to day programming journey.

This dotfiles provide configurations for Zsh, Neovim, Tmux, Alacritty (and some more). This configurations are "optimized" for developing in Python and Typescript (mainly React).

The color scheme used everywhere is Dracula.

Pre-flight checks

Make sure to install:

• asdf-vm
• vim-packager
• zplug
• tpm (Optional, only if you plan to use Tmux [highly recommended])

And these xstow xsel using your package manager

Installation

Just clone the repo and run Make

$ git clone git@github.com:richin13/dotfiles.git ~/dotfiles
$ cd ~/dotfiles
$ make dotfiles

Machine-local configuration

Use git freeze to keep a shared default for selected tracked files while allowing each machine to customize them locally. It stores the shared policy in the committed .git-freeze manifest and uses Git's local skip-worktree flag to hide machine-specific edits.

install -m 755 scripts/git-freeze ~/.local/bin/git-freeze

After cloning or pulling a manifest change, activate its paths locally:

git freeze apply

To declare a new tracked file, preserving any existing local edits:

git freeze add path/to/config
git add .git-freeze
git commit -m "Freeze machine-local configuration"

Inspect declared files with git freeze list. Use git freeze thaw path/to/config to temporarily expose its local changes, or git freeze unfreeze path/to/config to remove it from the shared policy.

Before updating, run git freeze check --fetch to see whether upstream changed any frozen files. git freeze sync fetches, stashes local overrides for affected files, fast-forwards the branch, reapplies those overrides, and freezes the files again. It refuses to run with non-frozen working-tree changes and leaves conflicting files thawed with the recovery stash intact.

Shared Skills

This repository supports shared agent skills stored once in ./agent-skills and linked into both:

• ./dotfiles/.agents/skills (Codex)
• ./dotfiles/.claude/skills (Claude Code)

Each skill must live in:

agent-skills/<skill-name>/SKILL.md

And SKILL.md must include frontmatter:

---
name: <skill-name>
description: <short description>
---

Bootstrap a new skill

Use the interactive bootstrap script:

./scripts/bootstrap-skill new

Or run it through Make:

make skill

Fix symlinks for an existing skill:

./scripts/bootstrap-skill fix <skill-name>

Remove a skill and its symlinks:

./scripts/bootstrap-skill rm <skill-name>

The bootstrap flow will:

• Ask for skill name and description
• Create ./agent-skills/<skill-name>/
• Create ./agent-skills/<skill-name>/SKILL.md with frontmatter
• Create/update symlinks in:
  • ./dotfiles/.agents/skills/<skill-name>
  • ./dotfiles/.claude/skills/<skill-name>

Aftermath

• (Map Caps Lock to Ctrl)[https://dev.to/tallesl/change-caps-lock-to-ctrl-3c4]

Troubleshoot

You might run into some issues when running make dotfiles. Under the hood, make will execute xstow to create the symlinks to the dotfiles. First make sure you have installed xstow

# When in LinuxMint (or any Debian based distro)
$ sudo apt install -y xstow

Mouse waking up the computer

Noticed Ubuntu 24 waking up from sleep when moving the mouse. Following this instructions fixes the issue:

The solution I'm using is a udev rule that disables wakeup from a particular USB device. It should be agnostic to which port the device is plugged in to.

Create /etc/udev/rules.d/90-usb-wakeup.rules with the following content (modify idVendor and idProduct as appropriate, see output from lsusb which gives the IDs in the form: vendor:product):

# Disable waking up from Logitech unified receiver
ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c52b", ATTR{power/wakeup}="disabled"

To get it applied without rebooting:

    Run:

    sudo udevadm control --reload-rules

    Disconnect and reconnect the USB device.

Inspiration comes from https://wiki.archlinux.org/title/udev#Waking_from_suspend_with_USB_device

https://askubuntu.com/a/1385877

Another issue you might run into is xstow not being able to create the symlinks. This happens when the files already exists in you home directory and are not symlinks. Make sure to backup your existing dotfiles before proceeding.

License

See LICENSE