Routa is a workspace-based coordination platform for delivering software with multiple AI agents, keeping goals, tasks, sessions, traces, evidence, and review decisions visible on a shared board. It is intended for teams managing agent-assisted development across web and desktop applications. The catalogue contains skills and instructions for working with Routa's delivery workflows.
Borrowing it
Nothing to install: this file belongs to phodal/routa. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/phodal/routa/main/.claude/skills/pr-verify/SKILL.mdgit clone --depth 1 https://github.com/phodal/routaWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/phodal/routa/pr-verify)<a href="https://agentmods.dev/skills/phodal/routa/pr-verify"><img src="https://agentmods.dev/badge/skills/phodal/routa/pr-verify/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/phodal/routa/pr-verify"><img src="https://agentmods.dev/badge/skills/phodal/routa/pr-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00043 | $0.00804 |
| Opus 5.5 | $0.00017 | $0.00322 |
| Sonnet 5.5 | $0.00009 | $0.00161 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
pr-verify scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Phases
Phase 1: Requirements Analysis
Parse PR body to extract:
- Acceptance Criteria: Checkboxes, numbered lists, "should" statements
- Linked Issues:
#123,fixes #456,closes #789 - Screenshots/Videos: Evidence of visual changes
- Breaking Changes: Migration notes, deprecation warnings
# Fetch PR details
gh pr view <PR_NUMBER> --json body,title,labels,linkedIssues
Phase 2: Review Comments Analysis
Fetch and categorize comments:
# Get all review comments
gh api repos/{owner}/{repo}/pulls/{pr}/reviews
gh api repos/{owner}/{repo}/pulls/{pr}/comments
Classify by status:
- Resolved: Addressed in subsequent commits
- Pending: Still needs attention
- Blocking: Marked as REQUEST_CHANGES
Phase 3: CI/Build Status Check
# Check all status checks
gh pr checks <PR_NUMBER> --json name,state,conclusion
# Get detailed check run logs if failed
gh api repos/{owner}/{repo}/check-runs/{check_run_id}
Required checks must pass:
- Build/compile
- Lint
- Type check
- Unit tests
- Integration tests (if applicable)
Phase 4: E2E Verification
Start services and run E2E tests:
# 1. Install dependencies (if needed)
npm install
# 2. Start dev server in background
npm run dev &
DEV_PID=$!
# 3. Wait for server ready
npx wait-on http://localhost:3000 --timeout 60000
# 4. Run E2E tests
npm run test:e2e
# 5. Cleanup
kill $DEV_PID
For Tauri apps:
npm run tauri dev &
# Use Playwright to interact with desktop window
Phase 5: Generate Report
Create verification summary:
# PR Verification Report
## Requirements Checklist
- [x] Feature A implemented (evidence: screenshot in PR)
- [x] API endpoint returns correct response
- [ ] ⚠️ Missing: Mobile responsive test
## Review Comments Status
- ✅ 3 resolved
- ⚠️ 1 pending (non-blocking suggestion)
- 🚫 0 blocking
## CI Status
| Check | Status |
|-------|--------|
| build | ✅ Pass |
| lint | ✅ Pass |
| test | ✅ Pass |
## E2E Verification
- ✅ Home page loads correctly
- ✅ User flow: login → dashboard works
- ⚠️ Note: Slow response on /api/data (>2s)
## Verdict
🟢 **READY TO MERGE** — All requirements verified
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 132 lines · 43 tokens per session scan A 7701df2db0c3
pr-verify is a skill published in the GitHub repository phodal/routa (1,830 stars, last pushed 13d ago), licensed MIT. It adds 43 tokens to every session and 804 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
test-conversion-reviewer
Reviewer for converting unit tests to browser tests for Project Bedrock. Invoke this when the user needs to review their work while removing complex Browser dependencies from tests.
ln-51-acceptance-test-builder
Builds, updates or retires scoped acceptance tests and verifies execution; does not repair product code.
playwright-e2e-review
Audit Playwright E2E tests in the gc.platform suite (tests/playwright) against the four hard rules — no mocks, Page Object Model, work-by-fixture, one folder per frontend feature module — plus strict-TypeScript quality. Use whenever the user wants to review, check, audit, or "make sure it follows the conventions" for…
test-case-coverage
Audits an already-automated test case (TC-XXX) — one end-to-end journey across several use cases — against its document and reports a coverage matrix: which Flow rows, Validation items, and postconditions have a test step and code behind them, which are still open, and which test steps have drifted away from the test…
triaging-visual-review-runs
Inspects PostHog Visual Review (VR) runs that gate PR merges with screenshot regression checks. Use when the user mentions "visual review", "VR", "snapshot diff", "screenshot test", "storybook regression", "playwright snapshot", "quarantine", asks why a PR is blocked or what changed visually, wants to triage the VR…
full-stack-e2e-review
Run a rigorous end-to-end product or feature review across architecture, data, APIs, permissions, billing, tests, and real browser UX. Use for requests such as review this branch end to end, test everything, ensure no bugs, perform a full visual pass, or validate a multi-user workflow before merge or deploy.