Claude-skill-registry benchmark-nvim
Benchmark Neovim startup time and identify slow plugins or configurations
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/benchmark-nvim" ~/.claude/skills/majiayu000-claude-skill-registry-benchmark-nvim && rm -rf "$T"
manifest:
skills/data/benchmark-nvim/SKILL.mdsource content
Neovim Startup Benchmark
Measure Neovim startup time and perform performance analysis.
Steps
1. Run benchmark with hyperfine
Execute the following command to measure startup time:
hyperfine --warmup 3 'nvim --headless +q'
2. Detailed analysis with startuptime
nvim --startuptime /tmp/nvim-startup.log --headless +q
Read
/tmp/nvim-startup.log and analyze:
- Total startup time: Time shown in the last line of the log
- Slowest plugins TOP 5: Items taking the most time in sourcing
- Phase breakdown:
- reading vimrc (init.lua)
- loading plugins
- syntax/filetype
- other
3. Output format
Report results in the following format:
## Benchmark Results ### hyperfine Results (Include hyperfine output as-is) ### Slowest Plugins TOP 5 | Rank | Plugin | Time (ms) | |------|--------|-----------| | 1 | xxx | X.XX | | ... | ... | ... | ### Phase Breakdown - init.lua loading: X.XX ms - Plugin loading: X.XX ms - Other: X.XX ms ### Optimization Suggestions (Provide suggestions based on slow plugins if applicable)
Notes
in hyperfine warms up the cache--warmup 3- Consider lazy.nvim lazy-loading settings in analysis