菜单
Scaffold a new tool configuration into this dotfiles repository — create the config under configs/, register the symlink in scripts/setup/symlinks.conf, and verify it. Use when the user wants to add config for a new tool, e.g. "add starship config", "set up delta config", or "add lazygit config".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | add-config |
| description | Scaffold a new tool configuration into this dotfiles repository — create the config under configs/, register the symlink in scripts/setup/symlinks.conf, and verify it. Use when the user wants to add config for a new tool, e.g. "add starship config", "set up delta config", or "add lazygit config". |
Scaffold a new tool configuration into this dotfiles repository.
Use when the user wants to add configuration for a new tool (e.g., "add starship config", "add lazygit config", "set up delta config").
Ask the user for:
starship, lazygit, delta)starship.toml, config.yml)~/.config/starship/starship.toml)Create the config directory and file under
configs/tools/<tool-name>/:
configs/tools/<tool-name>/<config-file>
Populate with sensible defaults or the content the user provides.
Register the symlink in scripts/setup/symlinks.conf —
this is the single source of truth for all symlinks.
Both setup-symlinks.sh and .tests/check.sh parse this file.
Add a line following the existing format:
configs/tools/<tool-name>/<config-file>|${HOME}/.config/<tool-name>/<config-file>
The format is: source_relative_path|${HOME}/target_path
Place the new entry in the # Tools section, keeping entries
in roughly alphabetical order. Look at existing entries for
reference — some tools use XDG paths (~/.config/<tool>/),
others use dotfiles in home (~/.<tool>rc). Match what the
tool actually expects.
For directory symlinks (when the whole config dir should be linked), point to the directory:
configs/tools/<tool-name>|${HOME}/.config/<tool-name>
Verify the source file exists in the repo (the path you just added to symlinks.conf must resolve to a real file or directory).
Test the symlink by running:
./scripts/setup/setup-symlinks.sh
Confirm the symlink was created at the target path.
If the tool is managed by mise, also add it to the
appropriate configs/tools/mise/conf.d/ file (see the
add-mise-tool skill for details on category selection
and version pinning).
symlinks.conf is the single source of truth — never
edit setup-symlinks.sh to add symlinks. The script reads
from symlinks.conf dynamically.symlinks.conf are relative to the
dotfiles root directory.${HOME} — never hardcode a literal
home path like /home/username.symlinks.conf format (pipe-delimited,
comments with #). Both setup-symlinks.sh and
.tests/check.sh parse it.configs/tools/, config file names matching
what the tool expects.~/.config/<tool>/ (XDG standard), others
use ~/.<tool>rc or ~/.<tool>.toml — match the tool's
actual expectation.scripts/install/ or mise conf.d/ files..zshrc.configs/shell/fzf/fzf.bash, configs/shell/fzf/fzf.zsh).Add, update, or remove a tool managed by mise in this dotfiles repository, including category placement and version pinning in configs/tools/mise/conf.d. Use when the user says "add ripgrep", "install lazygit", "add terraform", "bump node", asks which category a tool belongs in, or wants to remove a mise-managed tool.
Diagnose shell, terminal, and tooling issues in this dotfiles setup. Use when the user reports a problem like "my shell is slow", "colors are wrong", "completions do not work", "tmux keybindings broken", or "mise not loading".
Run a comprehensive health check on the dotfiles setup and produce a status report. Use when the user asks "is everything working?", "check my setup", "dotfiles doctor", or wants a general health report.
Explain what a configuration file does in plain language and flag what is safe to remove. Use when the user asks "what does this config do?", "explain my tmux config", or "what can I remove from .zshrc".
Replace one tool with another across the entire dotfiles setup. Use when the user wants to swap a tool for an alternative, e.g. nvm to mise, oh-my-zsh to antidote, vim to neovim, grep to ripgrep, or cat to bat.
Create a new POSIX-compliant shell script for this dotfiles repository following the required platform-detection and shellcheck patterns. Use when the user wants to add a script to scripts/ (install, setup, or utility) or any .sh file outside configs/, or needs a refresher on the required script patterns.