Read Notes Beside the Source
Each saved note appears through VS Code's native Comments UI beside the passage under review, with a Resolve action when the change is complete.
- Native inline comments
- Resolve action
- Source-linked notes
Open source · VS Code extension
Markdown Review Comments
Review specs, ADRs, and plans in VS Code with GitHub-style inline comments. Feedback stays in the Markdown file, durable anchors keep notes tied to the source, and unresolved comments export as context for an AI coding agent.
How Review Stays With the Document
The review surface, source position and handoff context remain part of the same local Markdown workflow.
- Native Inline Comments
- VS Code's native Comments UI places each review note beside a precise location in the Markdown document.
- Durable Anchors
- HTML-comment source anchors live inside the Markdown and move with the surrounding content as the document changes.
- Resolution
- Resolving a review note removes both the note and its source anchor, leaving the document ready for its next revision.
- Context Export
- Export Review Context collects the open feedback into an AI-readable handoff for the next editing pass.
What Stays Inspectable
Carry Feedback Through Git
Review data lives inside Markdown, making comments available to the branch, the repository history and tools that can read the document.
- Local-first storage
- Git-native review state
- AI-readable Markdown
Keep Review State in the Workspace
Review operations run in VS Code, Markdown stores the active notes, and Git records their history with the document.
- VS Code-native workflow
- Plain Markdown storage
- Git-backed history
Source, usage guidance and the extension architecture are public in the Markdown Review Comments repository.