Post Review Pickup

Authoritative protocol for next-lane pickup after ANY PR-lifecycle event boundary (review post, author response, implementation completion, PR open/update, ticket create, blocked-state resolution) AND for pre-review intake lane discovery from fresh boot or watchdog wake when no author lane is active. Prevents silent idle and reviewer-only cycles by requiring the next lane, a review-first rationale, or an explicit halt-state per §15.6 self-select mandate. Triggers: Use immediately after posting a PR review, chaining a formal GitHub review state, sending an author review-response commentId handoff, completing a discrete implementation chunk, opening/updating a PR, creating a ticket via create_issue, resolving a blocked-task-state (positive-path exit; negative-path entry remains blocked-task-state scope), OR before accepting the first PR review/re-review request in a fresh session/wake when no current author or implementation lane is claimed.

mkdir -p ~/.claude/skills/post-review-pickup
curl -L https://claudskills.com/skills/post-review-pickup/SKILL.md \
  -o ~/.claude/skills/post-review-pickup/SKILL.md

@misc{post-review-pickup-2026,
  author    = {neomjs},
  title     = {Post Review Pickup [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/post-review-pickup/}
}