ocr-review-to-approval-loop

Solid

Drive a PR to an approved code review by looping OCR's multi-agent review and address steps. Runs /ocr:review then /ocr:address repeatedly until the review verdict is APPROVE, then one final /ocr:address for leftover suggestions, posting every review and every address round to the GitHub PR as comments. Use when the user asks to 'review and address in a loop', 'iterate review until approved', 'auto review-and-fix this PR', 'loop /ocr:review and /ocr:address', or to take a changeset all the way to a clean APPROVE with the default reviewer team. Wraps the /ocr:review (.ocr/commands/review.md) and /ocr:address (.ocr/commands/address.md) skills; needs a feature branch with an open GitHub PR and the gh CLI for posting.

Code & Development 356 stars 28 forks Updated 1 months ago Apache-2.0

Install

View on GitHub

Quality Score: 85/100

Stars 20%
85
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# OCR Review-to-Approval Loop ## What This Skill Does Orchestrates an autonomous **review → address → re-review** loop on a pull request, using OCR's existing multi-agent review pipeline, until the review reaches an **APPROVE** verdict — then runs one final address pass for leftover suggestions. Every review and every address round is posted to the GitHub PR as a comment, producing a transparent, reviewable audit trail. It is a thin **orchestrator** over two skills it does not reimplement: - **`/ocr:review`** → `.ocr/commands/review.md` (the 8-phase multi-agent review that emits a verdict) - **`/ocr:address`** → `.ocr/commands/address.md` (corroborate feedback against code, then implement) ## When to Use - "Review and address in a loop until it's approved." - "Iterate /ocr:review and /ocr:address on this PR." - "Auto review-and-fix PR #N to a clean approval." ## When NOT to Use (use the underlying skills directly) - A **single** review with no auto-fixing → `/ocr:review`. - Addressing **one** existing review's feedback → `/ocr:address`. - There is no PR / not on a feature branch (this skill commits and posts). ## Prerequisites - On a **non-default** git branch with an **open GitHub PR** (the loop commits + pushes each round). - `gh` CLI installed and authenticated (for posting; skip with `--no-post`). - OCR set up in the repo (`.ocr/` exists, `ocr` CLI available). Run `/ocr:doctor` if unsure. - A green-ish working tree: any uncommitted changes will become part of wha...

Details

Author
spencermarx
Repository
spencermarx/open-code-review
Created
7 months ago
Last Updated
1 months ago
Language
TypeScript
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Featured

ocr

AI-powered multi-agent code review. Simulates a team of Principal Engineers reviewing code from different perspectives. Use when asked to review code, check a PR, analyze changes, or perform code review.

356 Updated 1 months ago
spencermarx
Code & Development Listed

address-review

Triage external code-review feedback on a merge request and resolve it end-to-end, automatically: decide which comments are valid against the actual diff (line by line), explain why each valid one was missed during coding, defend the correct decisions reviewers got wrong, then implement the fixes, push, and reply to every comment thread — all in one pass, without stopping to ask. Built for the loop where an AI coding agent writes the code, you raise an MR, and reviewer agents comment with less project context than the author has. Invoking the skill is the go-ahead for the whole loop (triage → implement → push → reply); the only hard stop is a red build. Valid comments get marked done on the MR, invalid ones explained. Use when: addressing MR/PR review comments, "address the review", "incorporate review feedback", triaging reviewer-bot comments, deciding which review comments are worth acting on.

0 Updated 1 months ago
ohyesgocool
AI & Automation Listed

address-review

Triages review comments on an open pull request — from humans and from bots (CodeRabbit, bugbot, Codex, Sourcery, …) — and addresses them. Reads every comment, verifies and challenges each one against the code, the frozen contract, and the ADRs to weed out false positives, then auto-fixes the trivial and gates the rest behind a plan. Manually invoked, standalone — not tied to a pipeline stage. Use when the user says "address the PR reviews", "go through CodeRabbit's comments", "handle the bugbot findings", "handle the codex findings" or "respond to the review".

1 Updated today
enocgit