stand-in-for-a-blocked-reviewlisted

Use when a pull request's automated review did not happen while its merge gate still reads green: the reviewer posted a quota or limit notice, skipped the pull request over who opened it, or never ran at all, and its status says success anyway. Confirms the review is genuinely missing, takes the cheap recoveries first, checks whether this exact content was already reviewed somewhere else, and only then commissions an independent agent review and posts it as the record. Do NOT fire when the reviewer posted findings (answer those instead), when the quota resets inside the time you can wait, or to decide whether the pull request should merge.
damson/hard-won-skills · ★ 1 · Code & Development · score 67

Install: claude install-skill damson/hard-won-skills

# Stand in for a blocked review A review bot's green mark has two meanings and nothing on the outside separates them: *reviewed and clean*, and *did not review*. A free-tier reviewer that has spent its quota writes "Review limit reached" into its comment and leaves its commit status at `success`. Nothing turns red, no gate blocks, and the pull request is indistinguishable from one that passed. That is not hypothetical. On the session this came from, a tier allowing one review per hour let three pull requests merge into a public repository believed reviewed, when nothing had read them. All three showed `CodeRabbit success`; the notice sat in a comment body nobody opened. This skill decides whether a review is actually missing, which is the step usually skipped, and then commissions one that is genuinely independent and posts it where a reader will look. ## Procedure 1. **Read the body, not the mark.** The mark answers a different question than the one being asked of it. Pin the head, then read what the reviewer actually wrote: ```bash pr=<n>; repo=<owner>/<repo>; reviewer=<reviewer-login> head=$(gh pr view "$pr" --json headRefOid --jq .headRefOid) # The gate can be a commit status OR a check run, and one API does not # show the other. A reviewer absent from check-runs may still be reporting # green as a status, which is what gates the merge. gh api "repos/$repo/commits/$head/status" --jq '.statuses[] | [.context, .state] | @tsv' gh ap