rotz-dotfiles_skill

Overview

This skill manages rotz-based dotfiles repositories, focused on a Fish-shell-first setup located at ~/.charmschool. It covers adding, configuring, and removing tools and apps, editing rotz configuration files (dot.yaml, defaults.yaml, config.yaml), and planning or executing structural changes to the dotfiles hierarchy. The guidance emphasizes idempotent installs, XDG-compliant configs, and safe use of the dot wrapper for operations.

How this skill works

The skill inspects the repo structure (agents/, apps/, tools/, shell/, editor/, lang/, git/) and the rotz metadata files (dot.yaml, defaults.yaml, config.yaml). It validates install/link patterns, detects inheritance from defaults.yaml, and ensures Fish-syntax in install commands where required. For changes it recommends creating or updating dot.yaml with installs, links, and depends keys, and updating references when moving items.

When to use it

• Adding a new CLI or GUI app to the repository (tools/, apps/, lang/).
• Creating or updating dot.yaml, defaults.yaml, or config.yaml entries.
• Restructuring directories or renaming dots and updating references across the repo.
• Converting tool config management to mise-managed workflows.
• Planning architectural changes to improve startup performance or grouping conventions.

Best practices

• Place new dots in the most logical existing group; propose a new group only if necessary.
• Prefer installs: null to inherit defaults.yaml where possible and use explicit install commands for special cases.
• Write Fish-idiomatic install commands (type -q, set -gx) and avoid bashisms.
• Keep install scripts idempotent, include error handling, and avoid exposing credentials.
• Document non-obvious decisions in comments and note macOS-specific variants.
• Use the dot wrapper (dot -i, dot -l, dot -a, dot --dry-run) instead of raw rotz where safer operations are desired.

Example use cases

• Add a new CLI tool: create tools/<name>/dot.yaml with installs: null or explicit installs, links to ~/.config, and depends if it needs another dot.
• Migrate language tooling to mise: add mise.toml, update lang/ entries, and ensure project-aware auto-loading.
• Restructure shell configs: move fish functions into shell/fish/functions/, update links in dot.yaml, and adjust defaults.yaml inheritance.
• Bootstrap a fresh machine: run sh bootstrap.sh, then dot -a to install and link all configured dots.
• Integrate fzf with fish: add fish functions, ripgrep type definitions, and configure keybindings via shell/fish and dot.yaml.