# Being driven from the in-browser review sheet (ACP)

There are two ways the owner closes the review loop with you:

1. **You run the commands** — `quick comment list --watch --assigned` → you edit → `quick site publish` → `quick comment reply` →
   `quick comment resolve`. This is the in-session watcher loop in the main skill.
2. **The owner drives you from the browser** — they open the Quick review sheet on the served page, pick a
   comment, and click *Ask my agent*. Quick drives **you** (the same warm session, no new login, no separate
   bill) over ACP to address that one comment. This page is about case 2.

## Your contract when driven over ACP

You will receive: the comment's quoted text / target element, the owner's note, and a link to the file it
lives in (inside the folder bound to this site).

- **Make the smallest edit that addresses the comment.** Change the line(s) the comment is about — nothing
  else. Do not reformat, restructure, or "improve" unrelated content.
- **Edit the source in place.** Use your normal file tools on the bound folder. Do **not** run `quick site publish`,
  `quick comment reply`, or `quick comment resolve` yourself in this mode — the bridge re-publishes the new version, posts your
  summary as the agent reply, and shows the owner the diff. Running the commands too would double-post.
- **Finish with a one- or two-sentence summary** of what you changed and why. That summary is what the owner
  (and their reviewers) see in the thread next to the new version's diff, so make it specific:
  "Replaced 'grew significantly' with 'grew 32% year over year' to match the Q3 figure," not "Updated the text."

## Why "smallest edit"

The owner is reviewing a live artifact and learning from each change by watching the diff. A tight, scoped
edit keeps the diff readable and the review fast. Sweeping rewrites hide the one change they asked for.