Extract Neovim LSP diagnostics and group code issues by severity.
npx skills add https://github.com/N0nki/dotfiles --skill nvim-diagnostics
Please help me install this Agent Skill. Skill: nvim-diagnostics Source: https://github.com/N0nki/dotfiles/tree/main/common/claude/skills/nvim-diagnostics Command: npx skills add https://github.com/N0nki/dotfiles --skill nvim-diagnostics
Neovim の LSP が検出したエラー、警告、情報、ヒントを取得し、コードの問題点と修正案を提案します。リクエストに応じて診断情報を分析し、修正を提案します。
Use this instruction to fetch the current buffer's LSP diagnostics and present actionable fixes.
High-intent search queries and answers about installing and using this skill.
Fetch Neovim LSP diagnostics to extract code errors, warnings, and hints from the current buffer or headless Neovim, then receive concrete fixes and implementation guidance for AI-assisted remediation.
Yes, Neovim LSP diagnostics can be retrieved via headless Neovim sessions, grouping items by severity and outputting structured results suitable for code investigations and on-demand diagnostic checks.
LSP diagnostics are grouped by severity—errors, warnings, information, and hints—then analyzed by root cause to present structured results with actionable fixes and best practices for code quality improvement.
Retrieve LSP diagnostics from the active buffer, group them by severity, and use AI-assisted remediation to analyze root causes and propose concrete fixes with implementation guidance.
No, diagnostics can be retrieved from the current active buffer during live editing sessions or via headless Neovim for on-demand diagnostic checks across related files.
rwaltrConfigure Neovim with Lua-based plugin management and LSP integration.
esneiderbravoAutomates Prettier and ESLint checks before Git commits and pushes.
NeKon69Manage code formatting and linting operations within the Neovim environment.
muzhicaomingwangExtract Reddit posts and comments and generate structured research reports.
