unioss-mr-feedbacklisted

# UNIOSS MR Feedback (main thread — writer) ## Overview Turn another developer's merge-request review comments into verified, tested, pushed fixes. Standalone: no ticket, no round, no gates, no `.walkthrough/` artifacts. Follow `../unioss-pipeline/REFERENCE.md` — its Branches, Protected-branch, Submodule, and Commit-message rules are binding. This skill is the second (and only other) place GitLab writes are permitted — see REFERENCE → GitLab: it may `git push` a feature branch; it must never create or merge an MR. **Core principle:** verify every comment against the code as it stands now — a reviewer's suggestion is not gospel just because someone else wrote it. **Track progress:** create a todo per Workflow step below and check each off as you complete it. ## Input - One or more GitLab merge-request URLs (`https://<host>/<namespace>/<repo>/-/merge_requests/<iid>`), extracted from the user's message. **Zero URLs found → ask the user for at least one before doing anything else.** Offer the ask as a short multiple-choice prompt where practical. ## Workflow (per MR URL) ### 1 — Fetch ```bash node "${CLAUDE_PLUGIN_ROOT}/skills/unioss-mr-feedback/scripts/fetch-mr-feedback.mjs" "<MR_URL>" ``` Prints the MR's state/branches/title, every non-system discussion thread (author, file:line, body, resolved/unresolved/not-resolvable), and the list of files the MR's diff touches. MR `state != opened` → report and skip this URL, continue with the rest. ### 2 — Resolve identity - R