resolve-feedbacklisted

# Resolve Review Feedback Fetch the unresolved review threads on an open change request, triage each one with the author, then act: change the code, reply on the thread, resolve it — in whatever combination each thread calls for. The goal is **resolution**: every thread ends fixed, answered, or resolved, not merely acknowledged. This closes the loop that `/anchor:prepare-review` opens: prepare-review routes reviewer attention out; resolve-feedback brings their findings back into the branch and drives each one to done. CR = change request: a pull request on GitHub, a merge request on GitLab. Pick the forge tool by the `origin` remote. **Don't narrate your work.** Every step below is an operating instruction, not a script to read aloud — follow the execute-quietly discipline: `${CLAUDE_PLUGIN_ROOT}/guides/execute-quietly.md`. For this skill, the only things worth surfacing are the resolved repo and CR in one line, each thread's triage, and what changed on it. ```mermaid %%{ init: { 'look': 'handDrawn' } }%% flowchart TD Start(["/resolve-feedback"]) --> Repo["Resolve repo + CR"] subgraph "Step 1: Fetch" Repo --> Fetch["Fetch unresolved threads"] Fetch --> Any{Any feedback?} Any -->|No| Stop([Nothing to address]) end subgraph "Step 2: Triage" Any -->|Yes| Present["Present threads + proposed dispositions"] Present --> Confirm{Author confirms?} Confirm -->|Adjust| Present end subgraph "Step 3: Act"