nvim-code-review
/nvim-code-review
Read and answer code review comments a human left in Neovim (code-review.nvim). Use when the user says "check comments", "address my review comments", or mentions code-review threads.
- Author
- muzomer ↗
- Repository
- code-review.nvim ↗
- Licence
- MIT
- Last repository change
- 11.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Read and answer code review comments a human left in Neovim (code-review.nvim). Use when the user says "check comments", "address my review comments", or mentions code-review threads.
Triggers from the description
Original author description
Read and answer code review comments a human left in Neovim (code-review.nvim). Use when the user says "check comments", "address my review comments", or mentions code-review threads.
How it works
- Workflow
- Reply format
- Rules
- Reviewing a PR (no checkout)
SKILL.md preview
---
name: nvim-code-review
description: Read and answer code review comments a human left in Neovim (code-review.nvim). Use when the user says "check comments", "address my review comments", or mentions code-review threads.
---
# nvim-code-review
The user leaves review comments on lines of code in Neovim. Each comment is a
**thread** with a stable id like `t_a3f9`. You read the threads, act on them,
and reply in the thread using the `code-review` CLI. Run all commands from
inside the project.
## Workflow
1. List the threads waiting on you:
`code-review list --needs agent`
Each thread shows its file, line range, the commented code, and the messages.
A comment on part of a line also quotes that text (`on "…"`): the comment is
about that text, not the whole lines.
Add `--json` for machine-readable output.
2. For each thread:
- Read the surrounding code in the file. Line numbers are current: the CLI
re-anchors threads to code that moved before listing them.
- Change code only for threads marked `change approved` (or when the prompt
you were given says to make the changes). For any other thread, even one
that asks for a change, do not edit files: reply with the change you
propose (a ```suggestion block, or a short description). The reviewer
approves it in Neovim, and the thread comes back to you marked approved.
An approval covers that one change: after your reply, the thread is
discuss-only again until the reviewer approves again.
- For an approved thread, make the change, then reply saying what you did.
- If it is a question or you disagree, reply with your answer. Do not resolve.
- If something is unclear, ask in the thread rather than guessing.
3. Reply:
`code-review reply t_a3f9 "Renamed to parse_config and updated callers."`
For long or multi-line replies, pipe the body on stdin:
`printf '%s' "$BODY" | code-review reply t_a3f9 -`
4. Resolve a thread only when the requested change is fully done:
`code-review resolve t_a3f9 "Done: extracted helper in utils.lua."`
## Reply format
Replies are GitHub-flavoured markdown, rendered in a small floating window in
the user's editor (about 80-100 columns). Keep them short and put the answer
first.
- Use `inline code` for identifiers, files and commands.
- Use fenced code blocks with a language tag for suggested code, and keep them
to the relevant lines. Prefer making the change over pasting it.
- To propose a replacement for exactly the commented lines (for example in a PR
review, where you cannot change the code), use a ```suggestion block holding
the new lines; the user sees it as a diff against the commented code.
- Short bullet lists are fine. No headings, tables, HTML, or images.
- Say what you changed and where (`utils.lua:40`), not a summary of the diff.
## Rules
- Never resolve a thread that is only a question or a discussion; reply and let
the user resolve it.
- Threads with status `outdated` point at code that no longer exists. Reply to
say whether the concern still applies; do not guess a new location.
- You may open a new thread to flag something to the user:
`code-review add src/foo.lua 42 48 "This loop is O(n^2); ok?"`
- One thread may be about the whole review instead of a line, shown as
`(the whole review: …)`: the user asks about the PR or the change as a whole
("what does this do?", "is this risky?"). Read the description and the diff
before answering, reply in it like in any thread, do not edit files for it,
and never resolve it.
- You cannot edit, reopen, or delete threads. Those are the user's.
- `code-review show <id>` prints one thread; `code-review list --all`
includes resolved ones.
## Reviewing a PR (no checkout)
When the user reviews a GitHub PR in Neovim there is no local checkout: the
changed files are snapshots in a cache directory. Add `--pr <PR URL | owner/repo#n>`
to **every** command, e.g.
`code-review --pr acme/api#12 list --needs agent`.
- `code-review --pr REF diff` starts with the PR **description** (read it first: it says what
the change is meant to do), then lists the changed files with `old:` (base commit)
and `new:` (head commit) snapshot paths. **Read code from those paths** with
your normal file tools; `--json` gives the same data.
- A file that is not in the snapshot (a caller, a helper, config) is fetched on
demand: `code-review --pr REF file src/utils.py` prints a path you can read.
`--side old` fetches the base-commit version. `code-review --pr REF ls src/`
lists a directory at the PR head.
- To find code that is not in the PR (callers, definitions, other uses), search
the repository on GitHub: `gh search code "<query>" --repo owner/repo`. It
searches the default branch, not the PR head: code the PR adds is in the
snapshots. Then fetch the files it finds with `code-review --pr REF file`.
- Comments other reviewers left on the PR on GitHub:
`code-review --pr REF github` (`--all` includes resolved ones). They are
context, not threads of yours: you may refer to them in a reply ("@bob
raised this too"), but you cannot answer or resolve them, and `list` never
shows them.
- Threads on removed or changed code may be on the **old side** (shown as
`(OLD side @abc1234)`): their line numbers refer to the base-commit snapshot.
To open one yourself: `code-review --pr REF add <old path> 12 "..." --side old`.
- You cannot change the PR. Where a thread asks for a fix, reply with the
explanation and a short suggested snippet; never claim you edited the PR.
Versions
The database has no other skills named nvim-code-review.
Database snapshot: 13.11.2026 · package version 559d4ae13705 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100nvim-install
Install Neovim and stand up the nvim-fredrik config in the Claude Code web sandbox (the cloud environment), where no Neovim exists. Use this before testing any Neovim config change in a web session, e.g. checking out a PR branch that touches nvim-fredrik and observing its… - 100obsidian-nvim
Guide for implementing obsidian.nvim - a Neovim plugin for Obsidian vault management. Use when configuring, troubleshooting, or extending obsidian.nvim features including workspace setup, daily notes, templates, completion, pickers, and UI customization. - 100neovim-configuration
Modern Neovim configuration expertise including Lua scripting, plugin management with lazy.nvim, LSP setup with Mason, AI integration with claudecode.nvim/opencode.nvim, and workflow optimization. Covers keymaps, autocommands, and treesitter configuration. Use when user mentions… - 100lazy-nvim-optimization
Profiles Neovim startup performance and optimizes lazy.nvim plugin loading with targeted lazy-loading specs, priorities, and event triggers. Contains profiling workflow and bottleneck checklists. Make sure to use this skill whenever the user mentions slow neovim startup, neovim… - 100neovim
Maintain the Stow-managed Neovim config in ~/.dotfiles/home/.config/nvim for Neovim 0.12+, lazy.nvim, vim.lsp.config, and nvim-treesitter main. Use to validate or repair Neovim, change plugins, diagnose measured startup regressions, or fix keymaps and LSP. Route whole-dotfiles… - 100nvim-tour
Teach a codebase step by step as a live guided course inside the user's Neovim. The agent writes the course, the bundled plugin (loaded ad hoc, never installed) shows each step beside the code, and the user sends questions back from Neovim. Use when the user asks to be taught,…