driving-cursor-bugbot

Drives the Cursor Bugbot fix-and-respond loop end-to-end. The canonical flow every PR author should run after Bugbot posts findings.

Why a skill

Cursor Bugbot's review surface is easy to mis-handle:

Replies must thread on the inline review-comment, not as a detached PR comment. A detached gh pr comment doesn't mark the thread resolved and the bot doesn't see it as a response.
Findings stale after fixes land. Bugbot reviews a specific commit SHA. When you push a fix, the comment still references the old commit; the thread stays open until you reply marking it resolved.
Stale findings vs. live bugs vs. false positives all read the same on the API surface. Triaging needs a process, not vibes.
Scope creep on PRs. CLAUDE.md mandates "When adding commits to an OPEN PR, update the PR title and description to match the new scope." Easy to forget when you're heads-down fixing Bugbot findings.

This skill makes all of the above mechanical.