Skip to main content
Execute qualquer Skill no Manus
com um clique
Repositório GitHub

dev-relay

dev-relay contém 8 skills coletadas de sungjunlee, com cobertura ocupacional por repositório e páginas de detalhe dentro do site.

skills coletadas
8
Stars
0
atualizado
2026-07-10
Forks
1
Cobertura ocupacional
3 categorias ocupacionais · 100% classificado
explorador de repositórios

Skills neste repositório

relay-dispatch
Outras ocupações de informática

Dispatch implementation tasks via worktree isolation. Use when delegating work to an executor, running background dispatches, or parallelizing independent tasks.

2026-07-10
relay-review
Analistas de garantia de qualidade de software e testadores

Use when completed relay executor work needs independent review against frozen Done Criteria — internal pre-publication rounds or post-publication PR rounds.

2026-07-10
relay-fleet
Desenvolvedores de software

Drive already-planned relay leaves through fan-out, review, serial merge, crash recovery, and fleet status.

2026-07-09
relay-config
Desenvolvedores de software

Interactive setup for relay routes. Use when the user asks to set up relay, configure company/personal relay routing, enable OpenCode or Pi, resolve model names, add provider/model routes, check advisory-review routing, or run relay-config doctor/check.

2026-07-08
relay
Desenvolvedores de software

Use when a GitHub issue, sprint item, task description, or natural-language handoff should be implemented through autonomous executor dispatch; stops at ready_to_merge — merge only on explicit request.

2026-07-08
relay-merge
Desenvolvedores de software

Merge a reviewed PR, clean up worktree/branch, and close GitHub issues. Use after relay-review returns LGTM.

2026-07-07
relay-plan
Desenvolvedores de software

Use when a relay run needs its review anchor, scored rubric, or dispatch prompt — always before relay-dispatch, whether AC are explicit, vague, or missing.

2026-07-06
relay-ready
Desenvolvedores de software

Verify a task is ready to relay — score readiness on clarity, granularity, and verifiability, then ask bounded questions when the task is too ambiguous to plan.

2026-07-05