← Pipeline

claude-builders-bounty Issue #4: PR Review Agent ($150)

Drafted
Reward: $150Platform: githubRail: opire (likely)Competition: ~622 claimants (high — many bot submissions expected)AI fit: highOpen issue ↗
Log time
Record payment (→ marks Paid)
Decision / notes
Read-only — unlock operator mode (top right) to edit.

Risk

| Risk | Assessment | |---|---| | Competition | HIGH — 600+ claimants; many may be low-quality bot PRs though | | Opire payment | UNCERTAIN — Opire was offline 2026-06-04T11:27Z; confirm before claiming | | Selected? | LOW-MEDIUM — but MINT's implementation is real+proven vs bot noise | | Effort to build CLI | LOW — 1 tick, ~$0 cost |

Deliverables (0)

None yet — MINT attaches the PR/claim text + code here once it builds.

Timeline

No events yet.

Full proposal (drafted by MINT)

# Proposal Draft — claude-builders-bounty Issue #4: PR Review Agent ($150)

> **Status**: DELIVERABLES COMPLETE — ready for operator to submit
> **DO NOT SUBMIT without operator approval** (per gig-earner guardrails)
> **Written**: 2026-06-04T11:44:41Z (G5 leaf, tick=635) | **Updated**: 2026-06-04T12:10:52Z (tick=638)

---

## Bounty Details

| Field | Value |
|---|---|
| Issue | https://github.com/claude-builders-bounty/claude-builders-bounty/issues/4 |
| Title | [BOUNTY $150] AGENT: Claude Code sub-agent that reviews a PR and posts a structured comment |
| Reward | $150 USD — powered by Opire |
| Claim mechanism | Post `/opire try` comment on issue, then submit a PR |
| Competition | ~622 claimants (high — many bot submissions expected) |
| Opire status | ⚠️ Was ECONNREFUSED at 2026-06-04T11:27Z — verify platform is functional before claiming |

## Why MINT Has a Unique Edge

**MINT already built this exact thing**: `bet-github-action-pr-reviewer-20260601` is a LIVE
GitHub Action at https://github.com/icgriggs14/github-action-pr-reviewer that:
- Takes a PR URL as input via `${{ inputs.pr_url }}`
- Uses Claude API to generate structured review (summary, risks, suggestions)
- Includes README with setup + sample output

The issue accepts EITHER a CLI tool OR a GitHub Action. MINT can deliver BOTH in 1 tick.

## Acceptance Criteria (from issue)

- [x] Works via GitHub Action (include the workflow YAML) — ALREADY DONE
- [ ] CLI wrapper: `claude-review --pr https://github.com/owner/repo/pull/123` — needs ~20 min work
- [x] Structured Markdown output: summary, risks, suggestions, confidence score
- [ ] Tested on 2 real GitHub PRs (include outputs in PR) — needs sample outputs generated
- [x] README with setup and usage instructions

## What MINT Built Autonomously ✅ (tick=638)

All deliverables are staged and ready:

1. ✅ **CLI wrapper** — `autonomy/projects/gig-earner/submissions/issue4-pr-agent/claude-review-cli/claude_review.py`
   - `python claude_review.py --pr <url>` — prints review to stdout
   - `python claude_review.py --pr <url> --post` — also posts as PR comment
   - Zero external dependencies (stdlib only)
   - Fetches diff via GitHub API → calls `claude-sonnet-4-20250514` → structured output

2. ✅ **CLI README** — `submissions/issue4-pr-agent/claude-review-cli/README.md`
   - Usage examples, output format, GitHub Action integration, requirements

3. ✅ **Sample review #1** — `submissions/issue4-pr-agent/sample-review-1.md`
   - knip-action PR #2 (real MINT repo)

4. ✅ **Sample review #2** — `submissions/issue4-pr-agent/sample-review-2.md`
   - github-action-pr-reviewer PR #1 (real MINT repo)

5. ✅ **GitHub Action** — already live at `icgriggs14/github-action-pr-reviewer`

## Operator Gate Required (all deliverables are ready — your 3 actions)

1. Verify Opire is operational (was confirmed online at 11:55Z — check `https://opire.dev`)
2. Fork `claude-builders-bounty/claude-builders-bounty` and submit a PR that adds:
   - `claude_review.py` + `README.md` (from `submissions/issue4-pr-agent/claude-review-cli/`)
   - `sample-reviews/` directory with the 2 sample outputs
   - Reference the live GitHub Action: `icgriggs14/github-action-pr-reviewer`
3. Post `/opire try` comment on issue #4 with your GitHub account
4. Collect payment via Opire if selected as winner

## Risk Assessment

| Risk | Assessment |
|---|---|
| Competition | HIGH — 600+ claimants; many may be low-quality bot PRs though |
| Opire payment | UNCERTAIN — Opire was offline 2026-06-04T11:27Z; confirm before claiming |
| Selected? | LOW-MEDIUM — but MINT's implementation is real+proven vs bot noise |
| Effort to build CLI | LOW — 1 tick, ~$0 cost |

## Pre-Submission Check

1. Verify Opire is operational: visit https://opire.dev
2. Check issue #4 for any "winner announced" or "closed" signal
3. If green: MINT builds CLI + sample outputs this tick → operator claims + submits PR

## Verdict

**Conditional GO**: If Opire is operational and issue #4 is still open for new submissions,
MINT should build the CLI wrapper + generate 2 sample PR reviews, then queue operator
to submit. MINT's edge is having a real, working implementation — not a bot-generated stub.

---

*Queued 2026-06-04T11:44Z by G5 leaf (tick=635)*