Individual skill

route

Detect the work type of a task or diff and dispatch the right specialist review/agent. Use when you're about to review or implement and want the correct domain reviewer (UI/design, API/devex, infra, docs, core) instead of a generic pass. The local mirror of the SDLC Classifier + domain-routed reviewers.

claude/skills/route/SKILL.md

Read pinned source

Source commit eb86da768cee325b0e89039b1f96ea29e29f2eb7

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Network or broad shell
Last checked: Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 21
Repository last updated: Nov 2, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai-agents Repository topic
claude Repository topic
claude-code Repository topic
codex Repository topic
developer-tools Repository topic
llm Repository topic
mcp Repository topic
subagents Repository topic
design Derived category
docs Derived category
design-interface Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 2,148 bytes

Read excerpt


# Route work to the right specialist

The cloud SDLC classifies each PR (`sdlc-classify.yml`) and runs domain-specific
reviewers. This skill does the same locally: classify, then dispatch.

## Steps
1. **Classify** the task/diff into ONE primary domain (default `core` if mixed):
   | Domain | Signals | Route to |
   |---|---|---|
   | `ui` | frontend, styling, components, UX | `code-reviewer` + a design/a11y pass |
   | `api` | public API/SDK, contracts, schemas | `code-reviewer` + contract/back-compat focus |
   | `infra` | CI, deploy, IaC, migrations | `k8s-operator` / careful review of blast radius |
   | `docs` | docs/markdown only | `docs-writer` |
   | `core` | library / business logic | `code-reviewer` (+ `security-auditor` if it touches authz/inputs) |