go-unifi

Address open code-review comments on a go-unifi GitHub Pull Request, one by one — understand each, then fix it, reject it with a reasoned objection, or ask a short clarifying question, replying in the thread like a thoughtful human teammate. Use this whenever the user wants to PROCESS, ANSWER, RESPOND TO, or ACT ON PR review feedback: "address the review comments", "go through the PR comments", "reply to the reviewer", "handle the feedback on #N", "someone left comments on my PR", "resolve the review", "fix what the reviewer asked". Trigger even when the word "comment" isn't used — any request to deal with, work through, or respond to reviewer/PR feedback means this skill. It is the usual next step after `unifi-2.0.0-wave` opens a PR, but works standalone on any PR. Do NOT trigger to CREATE a PR or implement issues (that's `unifi-2.0.0-wave`), to author issues (`unifi-issue-author`), or for the user asking how to review someone else's code.

Execute a go-unifi 2.0.0 migration wave end-to-end via a Claude Code Workflow. Use this whenever the user wants to DO 2.0.0 implementation work — "run a 2.0.0 wave", "next batch", "work issue #N", "implement the OpenAPI migration", "start the codegen retarget", "ship the next 2.0.0 PRs", or names any issue under epic #117 / milestone 2.0.0 and asks you to build it. Trigger even when the user doesn't say the word "wave": any request to implement, migrate, refactor, or PR something for 2.0.0 means a wave. Do NOT trigger for user-facing migration questions ("how do I upgrade to 2.0.0?") — that's the migration guide, not this.

Regenerate docs/2.0.0/coverage_matrix.md — the resource-centric API coverage table showing which UniFi resources are covered by the Legacy Internal API, the Official OpenAPI surface, or both. Use whenever the Official API groups or legacy resources change and the matrix needs to reflect the new state.

Author go-unifi 2.0.0 GitHub issues — the planning/authoring counterpart to unifi-2.0.0-wave. Use this whenever the user wants to CREATE or FLESH OUT work items rather than implement them: "create issues for 2.0.0", "decompose epic #117", "seed the next batch of issues", "plan the OpenAPI migration into tasks", "write acceptance criteria for #N", "this issue is too vague, flesh it out", "turn this into a proper issue", "what should the next wave's issues be?". Trigger even when the word "issue" isn't used — any request to plan, scope, slice, decompose, or write up 2.0.0 work as trackable tasks means authoring. Do NOT trigger to IMPLEMENT/build/PR work (that's unifi-2.0.0-wave) or for user-facing upgrade questions ("how do I migrate to 2.0.0?" — that's the migration guide).

Create conventional commits of changes. Use when asked to commit, save changes, create a commit, or when finishing implementation work. Also use when the user says "commit this", "save my work", "create commits", or just "/commit".