dev-env
Manage Jeremy's global dev environment (git, nvim, shell configs) and install tools. Use when asked to change global configs, add tools to the environment, or modify dotfiles.
When & Why to Use This Skill
This Claude skill automates the management and configuration of a global development environment. It enables seamless updates to dotfiles (Git, Neovim, Zsh), installation of new software packages via Nix, and maintenance of custom utility scripts, ensuring a consistent and optimized workspace for developers through automated workflows.
Use Cases
- Scenario 1: Updating global Git configurations or ignore patterns to maintain version control standards across all projects.
- Scenario 2: Configuring Neovim settings, plugins, and keybindings to enhance the integrated development environment (IDE) experience.
- Scenario 3: Installing and updating system-wide CLI tools and utilities by modifying Nix flake definitions and rebuilding the environment.
- Scenario 4: Customizing shell environments and terminal themes (Zsh, Ghostty, Starship) to improve command-line productivity and visual feedback.
| name | dev-env |
|---|---|
| description | Manage Jeremy's global dev environment (git, nvim, shell configs) and install tools. Use when asked to change global configs, add tools to the environment, or modify dotfiles. |
| context | fork |
Managing Jeremy's Dev Environment
Use this skill to make changes to Jeremy's global configs (git, nvim, shell, etc) or to install new tools into Jeremy's global environment. Only do this when Jeremy explicitly asks for it.
Repository Location
Jeremy's dev environment is managed through nix at ~/nix/public-base.
Directory Structure
config/— Config files organized by tool:git/— git config, ignore, attributesnvim/— neovim configurationzsh/— shell configghostty/— terminal configbat/,direnv/,starship.toml, etc.
flake.nix— Package definitions (what tools are installed)scripts/— Custom utility programsscripts.nix— Script definitions
Workflow
1. Check for uncommitted changes first
git -C ~/nix/public-base status
If there are uncommitted changes in the same files you need to edit, stop and ask Jeremy for instructions. If uncommitted changes are elsewhere, note them but proceed.
2. Make your edits
Edit the appropriate files in ~/nix/public-base/.
3. Install the changes
Run i to rebuild and install the nix environment.
4. Test the change
Test it yourself if possible, or ask Jeremy to test if it requires restarting the terminal or Claude Code.
5. Commit and push (if Jeremy approves)
Only commit your changes — don't include any pre-existing uncommitted changes.
Important: git push doesn't work due to a config issue. Use this instead:
git -C ~/nix/public-base push lol && git -C ~/nix/public-base pull