fish-shell-config

Fish shell functions and abbreviations let you create custom commands and shortcuts. Functions execute sequences of commands (like `ll` using `eza -la`), while abbreviations expand typed text (like `gst` expanding to `git status -sb`). Both persist across sessions when saved in your config.fish or conf.d directory.

Yes. Fish has different syntax for variables, conditionals, and loops than Bash. Migration involves translating idioms like variable expansion, array handling, and script structure. This Skill guides you through translating Bash patterns to Fish equivalents and setting up a compatible environment.

Use Fish's conf.d directory to split configuration into separate files by function or purpose, then source them from config.fish. This modular architecture makes maintenance easier, allows autoloading of functions, and works consistently across local machines and CI environments.

Fish distinguishes between session variables, universal variables (synced across sessions), and environment variables (exported to child processes). This Skill covers proper scoping, using `set -U` for persistence, and managing environment setup so configuration survives reboots and terminal restarts.

Fish allows prompt customization through the `fish_prompt` function and interactive configuration via the `fish_config` command. You can define custom prompts with colors, status indicators, and dynamic content, then save them to persist across sessions.

Yes. Fish autoloads functions from the functions directory, and you can write reusable scripts that work across local machines and CI environments. Proper variable scoping and modular conf.d sourcing ensure scripts run consistently without conflicts.