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.

90 days of the enterprise, pro and team plans free, no card needed. See the plans

OpenSmartRoute

git-pr-reviewer - Skill - OpenSmartRoute

Skillv1.0.0

git-pr-reviewer

Name: git-pr-reviewer
Author: onewave-ai

Review pull requests for code quality, security issues, and best practices. Use when reviewing PRs, checking code changes, or analyzing diffs before merge.

by onewave-ai(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from onewave-ai/claude-skills (git-pr-reviewer/SKILL.md). Install upstream with npx skills add onewave-ai/claude-skills --skill git-pr-reviewer. Copyright stays with the author.

Git PR Reviewer

Instructions

When reviewing a pull request:

Get the diff: Run git diff main...HEAD or git diff <base-branch>...HEAD
Analyze changed files: Identify all modified, added, and deleted files
Review each file for:
- Logic errors and bugs
- Security vulnerabilities (SQL injection, XSS, hardcoded secrets)
- Performance issues (N+1 queries, unnecessary re-renders, memory leaks)
- Code style and consistency
- Missing error handling
- Test coverage gaps

Review Checklist

Security

No hardcoded credentials or API keys
Input validation on user data
Proper authentication/authorization checks
No SQL injection vulnerabilities
XSS prevention in place

Code Quality

Performance

No unnecessary database queries
Efficient algorithms used
Proper caching where needed
No memory leaks

Testing

New code has tests
Edge cases covered
Tests are meaningful, not just for coverage

Output Format

## PR Review Summary

### Overview
[Brief summary of changes]

### Issues Found
#### Critical
- [Issue description + file:line]

#### Warnings
- [Issue description + file:line]

#### Suggestions
- [Improvement ideas]

### Approval Status
[APPROVE / REQUEST CHANGES / NEEDS DISCUSSION]

Example

# Review current branch against main
git diff main...HEAD --stat
git diff main...HEAD

Installed into a catalogue, chosen by a router

Install git-pr-reviewer 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.

Photo: RDNE Stock project

For the business

What it costs to adopt - in engineering time.

Same client, same code
One base URL
The OpenAI-compatible endpoint answers your existing SDK calls; model=auto lets the router choose.
The SDKs
One URL, every vendor
No vendor lock-in
Point your OpenAI-compatible client at one address; add, swap or retire providers in the catalogue without touching application code.
Every vendor side by side
Next eligible model answers
Failover built in
When a provider is down or over quota the request moves on; the trace says it did.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

onewave-ai-claude-skills-git-pr-reviewer.ocm.jsonjson

{
  "ocm": "1",
  "id": "onewave-ai-claude-skills-git-pr-reviewer",
  "kind": "skill",
  "name": "git-pr-reviewer",
  "description": "Review pull requests for code quality, security issues, and best practices. Use when reviewing PRs, checking code changes, or analyzing diffs before merge.",
  "publisher": "onewave-ai",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "coding",
      "data_analysis"
    ],
    "tags": [
      "skill-md",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Review pull requests for code quality, security issues, and best practices. Use when reviewing PRs, checking code changes, or analyzing diffs before merge."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/onewave-ai/claude-skills",
      "path": "git-pr-reviewer/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/onewave-ai/claude-skills/blob/HEAD/git-pr-reviewer/SKILL.md",
      "key": "onewave-ai/claude-skills/git-pr-reviewer/SKILL.md"
    },
    "allowed_tools": [
      "Read,",
      "Grep,",
      "Glob,",
      "Bash"
    ]
  },
  "instructions": "# Git PR Reviewer\n\n## Instructions\n\nWhen reviewing a pull request:\n\n1. **Get the diff**: Run `git diff main...HEAD` or `git diff <base-branch>...HEAD`\n2. **Analyze changed files**: Identify all modified, added, and deleted files\n3. **Review each file** for:\n   - Logic errors and bugs\n   - Security vulnerabilities (SQL injection, XSS, hardcoded secrets)\n   - Performance issues (N+1 queries, unnecessary re-renders, memory leaks)\n   - Code style and consistency\n   - Missing error handling\n   - Test coverage gaps\n\n## Review Checklist\n\n### Security\n- [ ] No hardcoded credentials or API keys\n- [ ] I",
  "cost": {
    "context_tokens": 404
  }
}

Fetch it by URL: GET /api/v1/registry/onewave-ai-claude-skills-git-pr-reviewer/manifest?version=1.0.0