miki-review-looplisted

Miki's personal pre-self-review loop. Iteratively runs /review on the current PR and addresses obvious issues until only minor nits remain or 3 iterations have run. Surfaces judgment calls back to the user, makes atomic commits per project convention, pushes once at the end. Invoke when the user says "/miki-review-loop", "loop the review", "iterate on the review", or similar after a PR has been created.
mikiwiik/claude-code-skills · ★ 0 · Code & Development · score 78

Install: claude install-skill mikiwiik/claude-code-skills

# miki-review-loop ## What this does Automates the "review → address → re-review" cycle Miki runs on his own PRs before reading them himself. The loop terminates when no actionable non-nit issues remain, when 3 iterations have run, or when a judgment call surfaces. Always ends with a written summary listing every change made and every commit produced. ## Preconditions Before starting, verify in order: 1. **PR identification.** - **If the user passed a PR argument** — accept any of: bare number (`84`), hash form (`#84`), prose (`PR 84`, `PR #84`), or full GitHub PR URL (`https://github.com/<owner>/<repo>/pull/84`). Normalize to a bare number, then run `gh pr view <number> --json number,title,headRefName,baseRefName,state` to fetch its details, **announce** the PR being processed in a single line — e.g. `Processing PR #84 — "<title>" on <head> → <base>` — and proceed without asking for confirmation. The user already named the PR; re-asking is friction. - **If no PR argument was given**: derive it from the current branch via `gh pr view --json number,title,headRefName,baseRefName,state`. Announce the detected PR in the same format as the with-arg path — `Detected PR #N — "<title>" on <head> → <base>` — and **ask the user to confirm** before proceeding. Do not start the loop on an unconfirmed PR. If multiple PRs match or detection is ambiguous, list candidates and ask which one. - **If no PR exists or it's not OPEN** (in either case): stop and tell the user. 2. **Cl