chrome extension for azure devops

Code review feedback,
piped straight to your AI agent

Your AI wrote the code. Your team reviewed it. Close the loop: export every Azure DevOps PR comment — code highlights, suggestions & replies — to one agent-ready Markdown file, in one click. Paste it into Copilot, Cursor or Claude and the review implements itself.

open source·no account·no API key·nothing leaves your browser

the problem

Twenty review comments on AI-generated code. Now what?

You shipped the PR with an AI agent in minutes — then reviewers left feedback across a dozen files. Handing it back to the agent means rebuilding every thread by hand: Azure DevOps has no export, and resolved threads are collapsed out of view.

your-workflow.diff
for each of the 20 review threads:
copy the file path and line numbers
copy the highlighted code the reviewer selected
copy any code suggestions
copy the comment… and every reply
expand resolved threads you forgot were hidden
+click “Export feedback” — once

how it works

Three steps, zero setup

No account, no API key, no config file. Install it and it’s ready on every pull request.

01

Open the Files view

Go to your pull request and open the Files tab (all changes). The button appears in the PR header.

02

Click “Export feedback”

The main button exports unresolved threads; the dropdown exports all — including Resolved, Closed, Fixed & Won’t Fix.

03

Paste into your AI agent

The Markdown lands on your clipboard and downloads as pr-feedback-<id>.md — with agent instructions built in. Paste as-is; no prompt to write.

agent-ready

Paste it. That’s the whole prompt.

Every export begins with battle-tested instructions for your AI agent — no prompt writing needed. The agent analyzes before it edits, skips bad suggestions with reasons, and drafts a one-line reply for every reviewer comment.

pr-feedback-142.md · built-in agent instructions
**Instructions for the AI coding agent** I have received code review feedback on this pull request; the threads are below. Please: 1. **Deep-analyze first.** Read each comment together with the referenced file, line range and highlighted code before changing anything. 2. **Act only on Active / unresolved threads.** Resolved or Closed threads below are context and reference only. 3. **Implement each suggestion carefully, without breaking existing behavior.** A single comment may require multiple changes… 4. **Change only what makes sense.** If a suggestion should not be applied, skip it and give a clear reason instead. 5. **Keep docs and code comments in sync.** 6. **When done, reply with a one-line, non-technical summary per addressed comment** so I can post it back to the reviewer.
analyzes before editingskips bad suggestions, with reasonsdrafts your replies to reviewers

features

Nothing lost from the review

Every export reconstructs the full context an AI agent needs to act on each comment.

Exact file & line context

Every thread carries its file path and line number or range — the agent knows exactly where to act.

Highlighted diffs, verbatim

The code the reviewer selected, with +/ markers and code fences preserved intact.

Code suggestions included

Reviewer suggestions are captured as ready-to-apply code blocks, not screenshots or paraphrases.

Whole threads, all replies

The original comment and every reply, with authors and timestamps — full conversation context.

Auto-expands hidden threads

Collapsed and resolved discussions are expanded before scraping, so nothing silently goes missing.

Clipboard + .md download

Every export is copied to your clipboard and saved as a Markdown file — whichever fits your flow.

output

What an export looks like

Clean, structured Markdown that pastes perfectly into any AI coding agent — or a wiki, a ticket, anywhere.

pr-feedback-142.md
# PR Feedback (PR !142) — 3 threads (all statuses) **Instructions for the AI coding agent** 1. Deep-analyze first… 2. Implement carefully… 3. Change only what makes sense… --- ## /src/config.json — lines 5-6 · Active **Highlighted code** ``` 5 "on_failure": [ - 6 "oncall@example.com" + 6 "sre-team@example.com" 7 ], ``` **Sam Carter** — 2026-05-12T00:57Z > Please point these alerts at the on-call distribution list. **↳ Reply — Priya Patel** — 2026-05-12T07:24Z > Good catch — updated in the latest push. ## /src/sync/job.py — line 48 · Resolved **Code suggestion** ```python retries = Retry(total=3, backoff_factor=0.5) ``` **Sam Carter** — 2026-05-12T01:03Z > Wrap the sync call with retry + exponential backoff.

Private by design

It reads the PR page you’re already viewing, builds the Markdown in your browser, and hands it to you. That’s the whole data flow.

no serversno trackingno analyticsno special permissionsno data collected

Read the privacy policy →

$ export review --to markdown --for ai

Ship the review, not the copy-paste

If it saves you an afternoon, star it on GitHub and share it with your team — that’s how other devs find it.