PR Respond

Apply the agreed code changes for the review items the user picked, then post the reply, reaction, and (for inline threads) thread resolution — all after a single confirmation.

Prerequisites

This skill consumes the prior pr-feedback triage from the conversation. Each selected item carries:

• disposition — fix (apply the change) / reply (answer, no change) / decline (won't fix) / defer (track for later)
• inline-thread id — GraphQL node id (from §2 of pr-feedback), needed to resolve the thread
• first-comment databaseId — needed for the reply and reaction endpoints
• owner / repo / PR number

If that context is absent (no triage in this conversation), run pr-feedback first — this skill does not re-fetch.

Selecting is not forcing a fix. "apply all" / "apply all P1" / picking items means act on each per its disposition — only fix items get a code change. The verb fix is reserved for actually changing code; it is never how the user selects items. When the user's instruction contradicts a disposition (e.g. "apply all" over a decline item), the disposition wins — flag the mismatch in the batch preview ("you said apply, but this was recommended decline: replying without a code change — say so if you want to force a fix") rather than silently editing.

Replies are drafted through the humanizer skill (see below) — that dependency is mandatory, not optional.