菜单
Validate POSIX compliance of shell scripts in this dotfiles repository and run shellcheck. Use when the user asks to check POSIX compliance, lint shell scripts, or before committing changes to .sh files in scripts/ or lib/.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | posix-check |
| description | Validate POSIX compliance of shell scripts in this dotfiles repository and run shellcheck. Use when the user asks to check POSIX compliance, lint shell scripts, or before committing changes to .sh files in scripts/ or lib/. |
Validate POSIX compliance of shell scripts in this dotfiles repository.
Use when the user asks to check POSIX compliance, lint shell
scripts, or before committing changes to *.sh files in
scripts/ or lib/.
Identify which shell scripts were changed or should be checked:
git diff --name-only HEAD
to find changed .sh files, falling back to all .sh
files in scripts/ and lib/.For each .sh file (excluding configs/ directory), verify:
#!/bin/sh
(not #!/bin/bash or #!/bin/zsh)[ ] not [[ ]]name() {} not function name$(( )) not (( ))local: Uses _underscore_prefixed variable
names instead of local>/dev/null 2>&1 not &>Run shellcheck --shell=sh on each file and report results.
Summarize findings: list passing files, failing files with specific violations, and suggested fixes for each violation.
configs/ (especially *.zsh) are exempt —
they may use Zsh features.fzf.bash and fzf.zsh files in
configs/shell/fzf/ are auto-generated and must NOT
be modified.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.
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".
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.