Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Review Notes EnhancedNew to Visual Studio Code? Get it now.
Review Notes Enhanced

Review Notes Enhanced

Solar Sun

|
2 installs
| (0) | Free
Review Notes-style inline code review notes with resilient code anchors, solved archive, and Git branch isolation.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Review Notes Enhanced

A Review Notes-style VS Code extension with resilient code anchors, a solved archive, and Git-branch-specific storage.

Add a note from the editor gutter

  1. Open a file inside the workspace.
  2. Move the mouse over the left gutter beside the line you want to review. VS Code displays its native + button.
  3. Click +, type the review comment in the inline Comments editor, then choose Add.
  4. Use Cancel to discard the draft. Existing notes use the same inline editor with Save and Cancel actions.

You can also add notes with Ctrl+Shift+N (Cmd+Shift+N on macOS), or from the editor right-click menu. The native gutter button is provided by VS Code's Comments API, not by a static gutter image.

Features

  • Native + button in the editor gutter when hovering over any line; the inline VS Code Comments editor is used to enter the note.
  • Plain Markdown review text with inline hover previews and a Review Notes tree grouped by file. No type or priority tags are required.
  • Persistent note threads are recreated from the active branch's local note store when VS Code starts or the Git branch changes.
  • Track comments through edits made in VS Code. Insertions/deletions before a note move its anchor; edits intersecting the anchor trigger a conservative context-based re-match.
  • Show stale notes explicitly rather than silently moving a comment to an unreliable location.
  • Mark Solved is available from the note's inline comment actions, the tree view, and the ✓ Mark Solved CodeLens. A solved note disappears from active lists and editor threads, and moves into Solved Archive.
  • Restore an archived note to the active list, or permanently delete it.
  • Automatically update note paths after VS Code file renames.

Git branch isolation

When a folder is inside a Git repository, the extension uses the repository's current branch as part of the note-store identity. Each branch loads a separate JSON file. Switching branches in VS Code reloads the corresponding branch's active and solved notes. Detached HEAD uses a commit-specific scope.

Notes are stored in VS Code's global extension storage, keyed by repository path and branch. They do not create files in the working tree, do not make the repository dirty, and are local to the current VS Code profile/machine. They are not committed or automatically shared with teammates. A non-Git folder uses its own non-git note scope.

The extension relies on the bundled vscode.git extension API and also asks Git for the branch name. The Git extension is declared as an extension dependency so its API is available.

Existing Review Notes data

On first launch, if the extension's new branch-specific store does not yet exist, it checks for the configured legacy file (.notes.json by default). If found, it imports those notes once into the first branch opened and leaves the original file untouched. Other branches start with their own empty stores. Back up important notes before migrating.

Build and install

The source folder can be packaged with npx --yes @vscode/vsce package. For a one-file, offline generator that contains the complete extension source and requires only Node.js 14+, use the standalone generate-review-notes-enhanced.js script distributed alongside this project. Run node generate-review-notes-enhanced.js [output-directory]; it writes review-notes-enhanced-0.5.0.vsix without needing to copy the project folder or install npm packages.

Install the resulting .vsix through VS Code → Extensions → ... → Install from VSIX….

Current limitations

  • The first version scopes one repository per VS Code workspace folder (the repository containing the first workspace folder). Multi-root workspaces with several independent repositories are not yet independently scoped per folder.
  • Notes are local to the VS Code profile. They are not shared with other developers unless an export/import or shared-storage feature is added later.
  • Note anchors are currently line-based, with selected source text and surrounding context retained for tracking. The native Comments API thread is attached to the tracked line.
  • Large or ambiguous code rewrites may be marked Stale; use Re-anchor Stale Note after checking the proposed match.
  • The native + control is VS Code's Comments API UI. It appears when hovering over commentable lines in the editor gutter; its exact visual placement follows the active VS Code theme and editor UI.
  • The extension should be validated in a test workspace before being used as the sole copy of important review records.
  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft