review-commentslisted

# Review Comments Run `/code-review` against a pull request, draft one top-level review comment plus per-finding inline comments from its findings, get your approval, then post them as a single GitHub review under the configured account. ## 1. Load or bootstrap the repo config Read [docs/agents/review-comments.md](../../docs/agents/review-comments.md) for the account to post as and the `suggested_event` default. If that file doesn't exist yet, offer to create it: - **Account**: ask which GitHub account to post reviews as (its username). It doesn't need to be authenticated locally yet; see step 3. - **Suggested event**: propose `auto` (computed per-run, see step 6), shown to the user for confirmation like the drafted review itself. A fixed override (`approve` / `request_changes` / `comment`) is equally legitimate if the user prefers to always land on one event and adjust it manually at review time. Once confirmed, write the file and ask whether to commit it on the current branch, folded into whatever this session is already about, or on a separate branch as its own PR. Either is legitimate, don't assume. ## 2. Resolve the PR Optional PR number/URL argument; default to the current branch's open PR (`gh pr view`), mirroring `/pr`'s convention. Stop with a clear message if neither is given and none is found. Gather `number`, `baseRefName`, `headRefName`, `headRefOid`, `headRepositoryOwner`, and `isCrossRepository` via `gh pr view <number> --json number,baseRefName,headRe