菜单
Check cross-platform (Linux and macOS) compatibility after config or script changes. Use when the user edits a config and wants to verify it works on both platforms, or adds a tool or script that may have platform-specific behavior.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | sync-platform |
| description | Check cross-platform (Linux and macOS) compatibility after config or script changes. Use when the user edits a config and wants to verify it works on both platforms, or adds a tool or script that may have platform-specific behavior. |
Check cross-platform compatibility after config changes.
Use when the user edits a config and wants to verify it works on both Linux and macOS, or when adding a new tool/script that may have platform-specific behavior.
Identify changed files: Use git diff --name-only
(or user-specified files).
Classify each change by platform sensitivity:
Shell scripts in scripts/ and lib/: Must use
scripts/utils/platform.sh guards. Check for:
apt, brew) without
is_linux/is_macos guards/usr/share/, /etc/) vs macOS
paths (/usr/local/, /opt/homebrew/)sed -i '' vs sed -i, grep -P on macOS)install_pkg and pkg_installed helper usage
instead of raw package manager callsZsh configs: Check for:
eval or source paths
(e.g., brew shellenv on macOS only)xclip/xsel (Linux) vs
pbcopy/pbpaste (macOS)notify-send (Linux) vs
osascript (macOS)Tmux config: Check for:
xclip vs pbcopy)open (macOS) vs xdg-open (Linux)Neovim config: Check for:
xclip vs pbcopy)Tool configs (configs/tools/): Generally portable,
but check for:
Read scripts/utils/platform.sh to understand
available detection functions and helpers.
Report findings:
For each file, state whether it's platform-safe or has issues
Show the specific lines with portability problems
Suggest fixes using the existing platform detection pattern:
if is_macos; then
# macOS-specific
elif is_linux; then
# Linux-specific
fi
For Zsh files, suggest
[[ "$OSTYPE" == darwin* ]] /
[[ "$OSTYPE" == linux* ]] guards
Verify fixes pass shellcheck --shell=sh for any
.sh files modified.
scripts/ and lib/ must be POSIX-compliant —
use scripts/utils/platform.sh functions.configs/ may use Zsh-specific syntax
([[ ]], arrays, etc.).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.