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 - Prompt - OpenSmartRoute

Name: review
Author: anh-ht93

Prompt file imported from anh-ht93/yaea-app (.claude/commands/review.md). Copyright stays with the author.

/review - Post-Implementation Review

Run Phase 5 review to verify implementation aligns with documentation.

Usage

/review <feature-number>

Example: /review f1 or /review 1

Steps

1. Load Feature Spec

Read YAEA/docs/features/f<number>-*.md to understand requirements.

2. Load Design Docs

Read in parallel:

YAEA/docs/design/component-inventory.md
YAEA/docs/design/color-palette.md
YAEA/docs/design/screens.md

3. Find Implementation Files

Search for feature implementation:

Views in YAEA/YAEA/Features/
ViewModels in same location
Tests in YAEA/YAEATests/

4. Run Review Checklist

Check	Source	Action
Code implements feature spec flow	Feature spec	Compare flows
All acceptance criteria have tests	Feature spec	Match tests to criteria
Components used match inventory	`component-inventory.md`	Verify names/signatures
Colors from palette only	`color-palette.md`	Check color usage
Architecture patterns followed	`architecture.md`	Verify MVVM+Repository
No business logic in Views	Code review	Check View files

5. Output Review Report

## Implementation Review: [Feature Name]

### Alignment Verification
- Feature spec <-> Code: [Aligned / Drift: list]
- Design docs <-> Code: [Aligned / Drift: list]
- Architecture <-> Code: [Aligned / Drift: list]

### Test Coverage
- Acceptance criteria covered: [X/Y]
- Missing tests: [list or "None"]

### Issues Found
| # | Issue | Priority | Fix |
|---|-------|----------|-----|
| 1 | [description] | [Critical/Medium/Low] | [action] |

### Review Result: [PASS / FAIL]

### Follow-up Actions (if FAIL)
1. [Specific fix required]

6. Prompt for Fixes

If issues found, ask:

"Which issues should I fix? (e.g., '1,2,3' or 'all' or 'none')"

Install review 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.

# /review - Post-Implementation Review Run Phase 5 review to verify implementation aligns with documentation. ## Usage ``` /review <feature-number> ``` Example: `/review f1` or `/review 1` ## Steps <required> Execute these steps in order. Do not skip any step. </required> ### 1. Load Feature Spec Read `YAEA/docs/features/f<number>-*.md` to understand requirements. ### 2. Load Design Docs Read in parallel: - `YAEA/docs/design/component-inventory.md` - `YAEA/docs/design/color-palette.md` - `YAEA/docs/design/screens.md` ### 3. Find Implementation Files Search for feature implementation: - Views in `YAEA/YAEA/Features/` - ViewModels in same location - Tests in `YAEA/YAEATests/` ### 4. Run Review Checklist | Check | Source | Action | |-------|--------|--------| | Code implements feature spec flow | Feature spec | Compare flows | | All acceptance criteria have tests | Feature spec | Match tests to criteria | | Components used match inventory | `component-inventory.md` | Verify names/signatures | | Colors from palette only | `color-palette.md` | Check color usage | | Architecture patterns followed | `architecture.md` | Verify MVVM+Repository | | No business logic in Views | Code review | Check View files | ### 5. Output Review Report ```markdown ## Implementation Review: [Feature Name] ### Alignment Verification - Feature spec <-> Code: [Aligned / Drift: list] - Design docs <-> Code: [Aligned / Drift: list] - Architecture <-> Code: [Aligned / Drift: list] ### Test Coverage - Acceptance criteria covered: [X/Y] - Missing tests: [list or "None"] ### Issues Found | # | Issue | Priority | Fix | |---|-------|----------|-----| | 1 | [description] | [Critical/Medium/Low] | [action] | ### Review Result: [PASS / FAIL] ### Follow-up Actions (if FAIL) 1. [Specific fix required] ``` ### 6. Prompt for Fixes If issues found, ask: > "Which issues should I fix? (e.g., '1,2,3' or 'all' or 'none')" <forbidden> - Skipping the feature spec read - Reporting PASS when issues exist - Auto-fixing without user confirmation </forbidden>

{ "prompt": "# /review - Post-Implementation Review\n\nRun Phase 5 review to verify implementation aligns with documentation.\n\n## Usage\n\n```\n/review <feature-number>\n```\n\nExample: `/review f1` or `/review 1`\n\n## Steps\n\n<required>\nExecute these steps in order. Do not skip any step.\n</required>\n\n### 1. Load Feature Spec\n\nRead `YAEA/docs/features/f<number>-*.md` to understand requirements.\n\n### 2. Load Design Docs\n\nRead in parallel:\n- `YAEA/docs/design/component-inventory.md`\n- `YAEA/docs/design/color-palette.md`\n- `YAEA/docs/design/screens.md`\n\n### 3. Find Implementation Files\n\nSearch for feature implementation:\n- Views in `YAEA/YAEA/Features/`\n- ViewModels in same location\n- Tests in `YAEA/YAEATests/`\n\n### 4. Run Review Checklist\n\n| Check | Source | Action |\n|-------|--------|--------|\n| Code implements feature spec flow | Feature spec | Compare flows |\n| All acceptance criteria have tests | Feature spec | Match tests to criteria |\n| Components used match inventory | `component-inventory.md` | Verify names/signatures |\n| Colors from palette only | `color-palette.md` | Check color usage |\n| Architecture patterns followed | `architecture.md` | Verify MVVM+Repository |\n| No business logic in Views | Code review | Check View files |\n\n### 5. Output Review Report\n\n```markdown\n## Implementation Review: [Feature Name]\n\n### Alignment Verification\n- Feature spec <-> Code: [Aligned / Drift: list]\n- Design docs <-> Code: [Aligned / Drift: list]\n- Architecture <-> Code: [Aligned / Drift: list]\n\n### Test Coverage\n- Acceptance criteria covered: [X/Y]\n- Missing tests: [list or \"None\"]\n\n### Issues Found\n| # | Issue | Priority | Fix |\n|---|-------|----------|-----|\n| 1 | [description] | [Critical/Medium/Low] | [action] |\n\n### Review Result: [PASS / FAIL]\n\n### Follow-up Actions (if FAIL)\n1. [Specific fix required]\n```\n\n### 6. Prompt for Fixes\n\nIf issues found, ask:\n> \"Which issues should I fix? (e.g., '1,2,3' or 'all' or 'none')\"\n\n<forbidden>\n- Skipping the feature spec read\n- Reporting PASS when issues exist\n- Auto-fixing without user confirmation\n</forbidden>", "variables": [], "notes": "Run Phase 5 review to verify implementation aligns with documentation.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/anh-ht93/yaea-app", "path": ".claude/commands/review.md", "ref": "4db32f0a83b07cbd3b9c154c8a78f36ae9482bef", "url": "https://github.com/anh-ht93/yaea-app/blob/4db32f0a83b07cbd3b9c154c8a78f36ae9482bef/.claude/commands/review.md", "key": "anh-ht93/yaea-app/.claude/commands/review.md" } } }

review

About

/review - Post-Implementation Review

Usage

Steps

1. Load Feature Spec

2. Load Design Docs

3. Find Implementation Files

4. Run Review Checklist

5. Output Review Report

6. Prompt for Fixes

Install review 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