Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

route

Estrelas15

Forks0

Atualizado30 de maio de 2026 às 04:40

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.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

dshakes

dshakes/compass

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	route
description	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.
argument-hint	[task description or 'review the current diff']
allowed-tools	Read, Grep, Glob, Bash

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

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)

Always run, regardless of domain: a correctness review (code-reviewer) and, for anything touching auth/inputs/tenancy/secrets, security-auditor. Routing only adds a targeted pass — it never removes the safety-critical ones.
Dispatch: hand the diff to the chosen subagent(s) in a fresh context; collect and summarize findings grouped Blocking / Should-fix / Nit.

Notes

Bias to more review when uncertain — misclassifying down is the only costly error.
This is advisory routing; it does not gate anything. The human still reviews and merges.
Model tiering (separate from domain routing): compass route "<task>" picks the cheapest-correct model (haiku/sonnet/opus). It's measured — compass route --eval scores it against scripts/route-evalset.tsv and CI gates on an accuracy floor, so the heuristic can't silently regress. Add real mis-routes to the set as they surface.

Mais deste repositório

mesmo repositório

using-compass

dshakes/compass

Use at the START of any task in a compass-enabled repo, or whenever you're unsure which capability fits. Indexes compass's guardrails, red-team, router, commands, subagents, and skills so you reach for the right tool instead of working ad-hoc. Read this before hand-writing config, reviewing a diff, adding a dependency, picking a model, or running untrusted code.

2026-07-2715

pr-shepherd

dshakes/compass

Take every open PR end-to-end — diagnose failing checks, classify them (real defect vs mechanical vs environmental), fix the mechanical ones on the PR branch, re-verify, and stop at the merge gate. Use on demand ("handle the open PRs") or on an interval via /loop (e.g. "/loop 15m /pr-shepherd"). Merges only when the human has granted merge authority in the current session; otherwise reports ready-to-merge.

2026-07-2615

morning-triage

dshakes/compass

Discovery for an autonomous loop — find this turn's work instead of being handed it. Reads what changed since the last run (failed CI, new issues, merged commits), judges what's actually worth acting on, writes findings to a durable state file, and hands each off to the SDLC loop with a stop-condition. Use as the first move of a scheduled loop, or by hand to plan a session. Read-only on code; never edits, opens PRs, or merges.

2026-06-2915

systematic-debugging

dshakes/compass

Use when something is broken — a failing test, panic, stack trace, error log, or wrong behavior whose cause isn't obvious. Reproduce it, form a hypothesis, PROVE the cause before changing code, then make the minimal root-cause fix and guard it with a test. For deep cases, hand off to the debugger subagent.

2026-06-0515

verification-before-completion

dshakes/compass

Use before claiming ANY task done, fix verified, check passing, or PR ready. Establish how the change is checked and actually run it — tests, typecheck, lint, the local gate, or the app itself — and observe it pass. Never report "should work" or pass along a subagent's unproven claim.

2026-06-0515

harden

dshakes/compass

Run the toolkit's security commands in order to surface secrets, MCP supply-chain issues, install drift, release provenance gaps, and untrusted-code risks before shipping. Use before opening a PR, after adding a dependency, or whenever the security posture needs a fresh check.

2026-06-0115

name	route
description	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.
argument-hint	[task description or 'review the current diff']
allowed-tools	Read, Grep, Glob, Bash

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

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)

Always run, regardless of domain: a correctness review (code-reviewer) and, for anything touching auth/inputs/tenancy/secrets, security-auditor. Routing only adds a targeted pass — it never removes the safety-critical ones.
Dispatch: hand the diff to the chosen subagent(s) in a fresh context; collect and summarize findings grouped Blocking / Should-fix / Nit.

Notes

Bias to more review when uncertain — misclassifying down is the only costly error.
This is advisory routing; it does not gate anything. The human still reviews and merges.
Model tiering (separate from domain routing): compass route "<task>" picks the cheapest-correct model (haiku/sonnet/opus). It's measured — compass route --eval scores it against scripts/route-evalset.tsv and CI gates on an accuracy floor, so the heuristic can't silently regress. Add real mis-routes to the set as they surface.