Skip to main content
Run any Skill in Manus
with one click
GitHub repository

dev-relay

dev-relay contains 8 collected skills from sungjunlee, with repository-level occupation coverage and site-owned skill detail pages.

skills collected
8
Stars
0
updated
2026-07-10
Forks
1
Occupation coverage
3 occupation categories · 100% classified
repository explorer

Skills in this repository

relay-dispatch
computer-occupations-all-other

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
software-quality-assurance-analysts-and-testers

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
software-developers

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

2026-07-09
relay-config
software-developers

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
software-developers

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
software-developers

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

2026-07-07
relay-plan
software-developers

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
software-developers

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