resolve-commentslisted

# Resolve PR/MR Review Comments Work through all unresolved review comments from a pull request or merge request on GitHub, GitLab, Bitbucket Cloud, or Azure DevOps. > Invoke this skill via `$resolve-comments` or the `/skills` command. This skill is stateless: platform detection runs on every invocation. ## Step 0: Graphify Availability (mandatory if present) Before anything else, check whether the **Graphify** skill is available in the running agent for this project. These harnesses do not expose a skills registry. Treat Graphify as available only if the project clearly ships it (e.g. a `graphify` skill/command file under the project's skills directory or an entry in the agent config). If you cannot positively confirm it, treat Graphify as unavailable and proceed without it. If Graphify **is** available, using it is **mandatory** for this run. Wherever a later step requires understanding code, mapping relationships across files, or making a design decision, you MUST first run Graphify on the relevant input (the affected file(s), the PR/MR diff, or the surrounding module) and use the resulting knowledge graph to inform your work. This applies in particular to: - **Step 4** — understanding each comment in the context of the surrounding code. - **Step 4b** — every deferred item: build the graph for the item's scope before choosing and executing a design route. - **Step 6** — self-review: graph the diff to check cross-file impact. If Graphify is **not** available, procee