메뉴
Check and update documentation after config changes. Compares current config state against docs and keybinding tables. Use after modifying neovim config, zshrc, tmux.conf, or other dotfiles. Also responds to: "are my docs up to date", "check docs", "update documentation".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Review vendored dependency updates for supply chain attacks. Works on any code: zsh plugins, npm packages, git submodules, or arbitrary diffs. Responds to: "audit updates", "review vendor diffs", "check for supply chain attacks", "is this plugin update safe".
Check neovim plugin health and staleness against a tiered schedule. Web-searches GitHub for each due plugin's current status. Use when asked about plugin updates, maintenance, or when running periodic audits. Also responds to: "are my plugins up to date", "check for updates", "plugin health".
Full command reference for keybindings, aliases, shell commands, and tool usage. Use when the user asks "how do I...", "what's the shortcut for...", "what key does...", or references a command they can't remember. Also use when the user discovers a new command and wants to save it. Covers: neovim, tmux, zsh, git, cargo, opam, dune, uv.
Analyze shell and editor command history for efficiency improvements. Finds repeated patterns, missing aliases, workflow bottlenecks, and tool suggestions. Uses a local sanitization script as a trust boundary — no raw history ever reaches the API. Use when asked about: shell efficiency, aliases, workflow optimization, "what do I type too much", "speed up my workflow".
Lab notebook — capture analysis results, benchmarks, and findings into notes/
| name | doc-sync |
| description | Check and update documentation after config changes. Compares current config state against docs and keybinding tables. Use after modifying neovim config, zshrc, tmux.conf, or other dotfiles. Also responds to: "are my docs up to date", "check docs", "update documentation". |
| context | fork |
| disable-model-invocation | true |
| allowed-tools | Bash(git diff:*), Bash(cat:*), Bash(grep:*), Bash(find:*), Bash(ls:*) |
Check docs against current config state and propose updates.
Each row maps a document to the config files it tracks. When those config files change, the document may need updating.
| Document | Tracks | What to check |
|---|---|---|
.config/nvim/README.md | lua/vinceb/lazy.lua, after/plugin/*.lua, LSP config | Plugin list, keybinding tables, LSP server table |
.config/nvim/CLAUDE.md | Same + directory structure | Architecture notes, modification guidelines |
Root README.md | docs/, setup.sh, top-level structure | Docs index, setup instructions |
Root CLAUDE.md | All keybinding sources, .claude/skills/ | Tier-1 command reference, skills index |
docs/aliases.md | .zshrc | Alias definitions and descriptions |
docs/claude-code.md | .claude/ directory | Skill descriptions, settings |
Detect changes: Run git diff --name-only HEAD (unstaged) and
git diff --name-only --staged to find modified files. If no git
changes, ask the user what they changed or check recent commits with
git log --oneline -10 --name-only.
Match against manifest: For each changed file, find which documents track it using the table above.
Check each affected document, one at a time:
Propose updates: Show a diff for each document that needs changes. Present one document at a time — don't batch. Explain what changed and why.
Wait for approval before writing each update. Never batch-write multiple doc changes without per-file approval.
