How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

review_and_merge_pr - Prompt

Name: review_and_merge_pr
Author: UnderUndre

Prompt file imported from UnderUndre/undreseller (.github/prompts/review_and_merge_pr.prompt.md). Fill in {{arguments}} before use. Copyright stays with the author.

agent: review_and_merge_pr

User Input

{{arguments}}

Optional arguments:

Specific PR number (e.g. 42 or #42)
--auto-merge (merge immediately if review PASS and tests GREEN)
--oldest-first (default: process PR queue from oldest to newest)

ultrathink

"Мержить говнокод в main — это всё равно что залить цемент в фановый стояк. Сначала опрессовка и прочистка, потом подпись и запуск." — Valera

Goal

Automate the audit, review, and merging of GitHub Pull Requests using gh CLI.
Ensures no untested, unreviewed, or broken code reaches main.

Operating Constraints

USE gh CLI FOR ALL PR OPS: gh pr list, gh pr diff, gh pr review, gh pr merge.
APPLY ADVERSARIAL REVIEW STANDARDS: Run /code_review multi-pass audit on PR diff before approving.
NEVER FORCE MERGE BROKEN CI: Verify GitHub Actions / CI status (gh pr checks) before merging.

Execution Workflow

1. Identify PR Queue

If PR number provided in {{arguments}} → target PR #<N>.
Else → query open PRs: gh pr list --state open --sort created --order asc --limit 10.

2. Fetch PR Context & Diff

For target PR:

Checkout or inspect diff: gh pr diff <PR_NUMBER>
Check CI status: gh pr checks <PR_NUMBER>
Read PR description and linked issues.

3. Execute Adversarial Audit

Run multi-pass inspection on PR diff:

Pass 1: Security (secrets, injections, unmasked PII)
Pass 2: Concurrency (race conditions, async rejections)
Pass 3: Resource Leaks (unclosed streams/pools, N+1 queries)
Pass 4: Anti-Slop (redundant defensive code, dead wrappers)

4. Post Review Comment / Verdict

If BLOCKER / CRITICAL issues found:
Post review requesting changes: gh pr review <PR_NUMBER> --request-changes --body "<formatted findings>"
If zero critical issues and CI checks PASS:
Post approval: gh pr review <PR_NUMBER> --approve --body "LGTM — Adversarial audit passed without critical risks."

5. Merge Execution (If Authorized)

If approved and user specified --auto-merge or confirmed merge:

Execute squash/rebase merge: gh pr merge <PR_NUMBER> --squash --delete-branch
Output: "PR # merged successfully. Branch deleted."

Install review_and_merge_pr and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

--- agent: review_and_merge_pr --- ## User Input ```text {{arguments}} ``` Optional arguments: - Specific PR number (e.g. `42` or `#42`) - `--auto-merge` (merge immediately if review PASS and tests GREEN) - `--oldest-first` (default: process PR queue from oldest to newest) ultrathink > "Мержить говнокод в main — это всё равно что залить цемент в фановый стояк. Сначала опрессовка и прочистка, потом подпись и запуск." — Valera ## Goal Automate the audit, review, and merging of GitHub Pull Requests using `gh` CLI. Ensures no untested, unreviewed, or broken code reaches `main`. --- ## Operating Constraints 1. **USE `gh` CLI FOR ALL PR OPS**: `gh pr list`, `gh pr diff`, `gh pr review`, `gh pr merge`. 2. **APPLY ADVERSARIAL REVIEW STANDARDS**: Run `/code_review` multi-pass audit on PR diff before approving. 3. **NEVER FORCE MERGE BROKEN CI**: Verify GitHub Actions / CI status (`gh pr checks`) before merging. --- ## Execution Workflow ### 1. Identify PR Queue - If PR number provided in `{{arguments}}` → target PR `#<N>`. - Else → query open PRs: `gh pr list --state open --sort created --order asc --limit 10`. ### 2. Fetch PR Context & Diff For target PR: - Checkout or inspect diff: `gh pr diff <PR_NUMBER>` - Check CI status: `gh pr checks <PR_NUMBER>` - Read PR description and linked issues. ### 3. Execute Adversarial Audit Run multi-pass inspection on PR diff: - **Pass 1:** Security (secrets, injections, unmasked PII) - **Pass 2:** Concurrency (race conditions, async rejections) - **Pass 3:** Resource Leaks (unclosed streams/pools, N+1 queries) - **Pass 4:** Anti-Slop (redundant defensive code, dead wrappers) ### 4. Post Review Comment / Verdict - If `BLOCKER` / `CRITICAL` issues found: Post review requesting changes: `gh pr review <PR_NUMBER> --request-changes --body "<formatted findings>"` - If zero critical issues and CI checks PASS: Post approval: `gh pr review <PR_NUMBER> --approve --body "LGTM — Adversarial audit passed without critical risks."` ### 5. Merge Execution (If Authorized) If approved and user specified `--auto-merge` or confirmed merge: - Execute squash/rebase merge: `gh pr merge <PR_NUMBER> --squash --delete-branch` - Output: "PR #<N> merged successfully. Branch deleted."

{ "prompt": "\n---\nagent: review_and_merge_pr\n---\n\n\n## User Input\n\n```text\n{{arguments}}\n```\n\nOptional arguments:\n\n- Specific PR number (e.g. `42` or `#42`)\n- `--auto-merge` (merge immediately if review PASS and tests GREEN)\n- `--oldest-first` (default: process PR queue from oldest to newest)\n\nultrathink\n\n> \"Мержить говнокод в main — это всё равно что залить цемент в фановый стояк. Сначала опрессовка и прочистка, потом подпись и запуск.\" — Valera\n\n## Goal\n\nAutomate the audit, review, and merging of GitHub Pull Requests using `gh` CLI. \nEnsures no untested, unreviewed, or broken code reaches `main`.\n\n---\n\n## Operating Constraints\n\n1. **USE `gh` CLI FOR ALL PR OPS**: `gh pr list`, `gh pr diff`, `gh pr review`, `gh pr merge`.\n2. **APPLY ADVERSARIAL REVIEW STANDARDS**: Run `/code_review` multi-pass audit on PR diff before approving.\n3. **NEVER FORCE MERGE BROKEN CI**: Verify GitHub Actions / CI status (`gh pr checks`) before merging.\n\n---\n\n## Execution Workflow\n\n### 1. Identify PR Queue\n\n- If PR number provided in `{{arguments}}` → target PR `#<N>`.\n- Else → query open PRs: `gh pr list --state open --sort created --order asc --limit 10`.\n\n### 2. Fetch PR Context & Diff\n\nFor target PR:\n\n- Checkout or inspect diff: `gh pr diff <PR_NUMBER>`\n- Check CI status: `gh pr checks <PR_NUMBER>`\n- Read PR description and linked issues.\n\n### 3. Execute Adversarial Audit\n\nRun multi-pass inspection on PR diff:\n\n- **Pass 1:** Security (secrets, injections, unmasked PII)\n- **Pass 2:** Concurrency (race conditions, async rejections)\n- **Pass 3:** Resource Leaks (unclosed streams/pools, N+1 queries)\n- **Pass 4:** Anti-Slop (redundant defensive code, dead wrappers)\n\n### 4. Post Review Comment / Verdict\n\n- If `BLOCKER` / `CRITICAL` issues found: \n Post review requesting changes: `gh pr review <PR_NUMBER> --request-changes --body \"<formatted findings>\"`\n- If zero critical issues and CI checks PASS: \n Post approval: `gh pr review <PR_NUMBER> --approve --body \"LGTM — Adversarial audit passed without critical risks.\"`\n\n### 5. Merge Execution (If Authorized)\n\nIf approved and user specified `--auto-merge` or confirmed merge:\n\n- Execute squash/rebase merge: `gh pr merge <PR_NUMBER> --squash --delete-branch`\n- Output: \"PR #<N> merged successfully. Branch deleted.\"", "variables": [ "arguments" ], "notes": "Optional arguments:", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/UnderUndre/undreseller", "path": ".github/prompts/review_and_merge_pr.prompt.md", "ref": "a8341c491fa4fbbd3a0297434ec5734495f4216f", "url": "https://github.com/UnderUndre/undreseller/blob/a8341c491fa4fbbd3a0297434ec5734495f4216f/.github/prompts/review_and_merge_pr.prompt.md", "key": "UnderUndre/undreseller/.github/prompts/review_and_merge_pr.prompt.md" } } }

review_and_merge_pr

About

agent: review_and_merge_pr

User Input

Goal

Operating Constraints

Execution Workflow

1. Identify PR Queue

2. Fetch PR Context & Diff

3. Execute Adversarial Audit

4. Post Review Comment / Verdict

5. Merge Execution (If Authorized)

Install review_and_merge_pr and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews