DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to get a verdict on every open PR before merging with Finn Loop

Run a reviewer loop that checks open PRs against their Linear issue and required checks, then posts a verdict.

Who it is forA developer who has agent-built PRs waiting and needs a consistent first-pass review before deciding whether to merge.

The problemReading every agent PR in full against its issue and CI status takes time, and it is easy to miss a missing acceptance criterion.

The outcomeEach open PR gets a three-group verdict. Only PRs marked loop-approved, conflict-free, and green on all required checks are candidates for the human merge.

What you need first

  • A Git repository hosted on GitHub with a working origin remote
  • Claude Code 2.1.71 or newer
  • A Linear workspace and team with the Linear connector enabled in Claude Code
  • The GitHub CLI (gh) authenticated with write access to the target repo
  • At least one required GitHub status check if you want fully automated loop-approved verdicts

Steps

  1. Start a second Claude Code session in the repo and run /loop /finn-review.
  2. Read the verdict each PR receives, including any loop-changes-requested or needs-human-review label.
  3. Merge only PRs that are loop-approved, conflict-free, and green on all required checks.
  4. For any needs-human-review PR, read and resolve the escalation reason before merging.

Prompt for your agent

In the GitHub repo at <repo path>, run /loop /finn-review on the open pull requests. Expected output: a three-group verdict posted on each PR with its Finn-loop label. Verify that each verdict names the linked Linear issue and the required checks it was measured against.

Caveat. loop-approved is evidence for the human merge decision, not permission to merge, and fully automated verdicts need at least one required GitHub status check.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page