Markdown annotation for VS Code and Copilot CLI.
Features
- AI-Powered Review: Copilot identifies reviewable items in your markdown documents
- Interactive Workflow: Walk through each item, make decisions with Accept/Reject/Skip/Question verdicts
- Structured Annotations: Verdicts recorded as GitHub-style
> [!COMMENT] callout blocks
- Dual Distribution: Works in VS Code (extension) and terminal (Copilot CLI)
- Resume Support: Pick up where you left off — already-annotated items are skipped
VS Code UI Components
The extension provides rich UI for manual annotation without AI:
- Quick-pick Command (
Ctrl+Shift+A / Cmd+Shift+A) — Select text, choose status, add optional comment
- Hover UI — Select text and hover to see clickable status buttons (
✓ Accept, ✗ Reject, etc.)
- CodeLens — Status indicators appear above each annotation block; click to navigate
- Sidebar Panel — Lists all annotations in the current file; click to jump to location
- Status Bar — Shows annotation count; click to reveal sidebar panel
- Context Menu — Right-click selected text → "Add Annotation"
Installation
VS Code Extension
Install from the VS Code Marketplace:
- Open VS Code
- Go to Extensions (Ctrl+Shift+X)
- Search for "Markdown Commenter"
- Click Install
Or install via command line:
code --install-extension erdem-tuna.markdown-commenter
Copilot CLI
For terminal users with GitHub Copilot CLI:
npx @erdemtuna/markdown-commenter install copilot
This installs the annotation agent and skill to ~/.copilot/.
Quick Start
VS Code
- Open a markdown file containing findings or recommendations
- Open Copilot Chat (Ctrl+Shift+I or click the Copilot icon)
- Say: "Annotate this document" or "@annotate help"
- Follow the interactive workflow to review each item
Copilot CLI
- In your terminal, start the annotation:
@annotate path/to/document.md
- Review each item as presented
- Enter your verdict: Accept, Reject, Skip, or Question
Annotations are written as GitHub-style callout blocks:
> [!COMMENT]
> **ID**: abc12345
> **Status**: Accept
> **Re**: "key finding text..." (optional)
>
> Your comment explaining the verdict.
Verdict Types
| Verdict |
Meaning |
| Accept |
Agree with the item |
| Reject |
Disagree or identify an issue |
| Skip |
Not relevant or defer for later |
| Question |
Need clarification before deciding |
Configuration
VS Code Settings
| Setting |
Description |
Default |
markdown-commenter.promptsDirectory |
Custom agent installation directory |
Platform default |
Platform defaults:
- Linux:
~/.config/Code/User/prompts/
- macOS:
~/Library/Application Support/Code/User/prompts/
- Windows:
%APPDATA%/Code/User/prompts/
Use Cases
- Document Reviews: Annotate audit reports, technical assessments, compliance documents
- Feedback Sessions: Review proposals, specs, or design documents with structured comments
- Meeting Notes: Process action items and decisions with clear verdicts
- Research Papers: Annotate findings and recommendations for later reference
Troubleshooting
Agent not appearing in Copilot Chat
- Reload VS Code window (Ctrl+Shift+P → "Reload Window")
- Check output channel: View → Output → "Markdown Commenter"
- Verify agent is installed: Check
~/.config/Code/User/prompts/ (Linux)
CLI installation issues
- Verify Node.js 18+:
node --version
- Check installation:
npx @erdemtuna/markdown-commenter list
- Reinstall:
npx @erdemtuna/markdown-commenter uninstall && npx @erdemtuna/markdown-commenter install copilot
Development
Build from source
git clone https://github.com/erdem-tuna/markdown-commenter
cd markdown-commenter
npm install
npm run compile
Run tests
npm test # Extension tests
cd cli && npm test # CLI tests
Lint agent files
npm run lint:agent:all # Lint agents and skills for token limits
Package extension
npm run package
Release process
Releases are automated via GitHub Actions:
- Extension: Push a
v* tag (e.g., git tag v1.0.0 && git push origin v1.0.0)
- CLI: Push a
cli-v* tag (e.g., git tag cli-v1.0.0 && git push origin cli-v1.0.0)
See CONTRIBUTING.md for maintainer setup (secrets, first-time publish, etc.).
Contributing
Contributions welcome! Please:
- Fork the repository
- Create a feature branch
- Make your changes with tests
- Submit a pull request
See the Code of Conduct for community guidelines.
License
MIT