Standardize Fish shell environments with centralized config.fish and conf.d structures.
npx skills add https://github.com/TophC7/dot.nix --skill fish
Please help me install this Agent Skill. Skill: fish Source: https://github.com/TophC7/dot.nix/tree/main/modules/home/common/claude/skills/fish Command: npx skills add https://github.com/TophC7/dot.nix --skill fish
Solves configuration inconsistency by standardizing the Fish shell environment.
Configure a minimal Fish setup that establishes PATH, defines a few aliases, and includes a simple fish_prompt function.
High-intent search queries and answers about installing and using this skill.
To migrate from Bash to Fish, you need to standardize your shell environment by translating existing configurations into a centralized structure using config.fish, conf.d, and autoloaded functions for a uniform UX.
The best way to organize Fish shell aliases and functions is by using a centralized config structure with config.fish and conf.d directories, ensuring consistency across different machines and development environments.
You can create a custom prompt in Fish shell by defining a simple fish_prompt function within your configuration, which helps boost productivity and standardize the visual shell environment.
Yes, Fish shell supports abbreviations alongside aliases and functions, providing guidance for creating these shortcuts to boost productivity while maintaining a centralized and consistent configuration structure.
You can set environment variables in Fish shell through a centralized config.fish file or conf.d directory structure, which ensures configuration consistency across machines and routine shell customization tasks.
wcyganConfigure Fish shell scripts, functions, abbreviations, and prompts.
a-ng-dGenerate shell completion scripts for Bash, Zsh, Fish, and PowerShell.
NJX-njxAutomate coding tasks and reviews via terminal-based AI coding agents.
haomingzGenerate and load glab CLI completion scripts for Bash, Zsh, Fish, and PowerShell.
