go

Dispatches ad-hoc coding demands to an isolated worker that returns a pull request.

20|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/reddb-io/red-skills --skill go-reddb-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: go
Source: https://github.com/reddb-io/red-skills/tree/main/plugins/dev/skills/engineering/go
Command: npx skills add https://github.com/reddb-io/red-skills --skill go-reddb-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Handling one-off, untracked coding requests often pollutes the tracked backlog or forces manual worktree, branch, and PR management. This Skill provides a middle dispatch tier between conversational steering and full backlog processing: it mints a disposable issue, spins a dedicated worker in an isolated worktree, runs review and validation gates, and brings back a PR — all through the daemon's MCP interface. ## Core Features & Use Cases - Approval-gated dispatch: Drafts a detailed Task and Definition of Done and requires explicit maintainer approval before any worker is dispatched. - Multiple dispatch modes: direct-PR (default), no-mistakes (hardened pre-PR pipeline), local-only (approved local fast-forward merge), and --scout for read-only investigations that post a report comment and mutate nothing. - Lane isolation and observability: Disposable issues carry lane:go or lane:scout labels so fleet drains never pick them up, and workers are stamped with origin=go/origin=scout for status tracking. - Use Case: A maintainer needs a quick one-off fix that should not become a tracked backlog item. They run /go "fix the flaky login test" --dod "test passes 10 consecutive runs", approve the drafted Task and DoD, and receive a PR that auto-closes the disposable issue on merge. ## Quick Start Ask the agent to dispatch an ad-hoc task with /go followed by your quoted demand, then approve the drafted Task and Definition of Done when prompted.

Frequently Asked Questions about go

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I dispatch a one-off coding task without creating a tracked issue?▼

Run /go with your demand as one quoted argument. The skill drafts a Task and Definition of Done for your approval, then dispatches a worker through the rs_dev MCP that mints a disposable lane:go issue and returns a PR.

What is the difference between /go, /goal, and /afk?▼

/goal handles unstructured conversational directives with no artifact, /go handles one concrete untracked demand producing a disposable issue and PR, and /afk processes the triaged tracked backlog. Anything that is or should be a tracked issue belongs to /afk, never /go.

How do I run a read-only codebase investigation without code changes?▼

Use /go --scout with your question as a quoted argument. The scout worker runs in read-only mode with commits and pushes disabled, posts its markdown report as a comment on a disposable lane:scout issue, and closes it.

Does +yolo skip the Task and Definition of Done approval step?▼

No. The +yolo token only raises the engine's in-run autonomy for that dispatch. The maintainer approval gate for the drafted Task and Definition of Done is always required before any code-producing /go dispatch.

Why does /go fail when the MCP tools are unavailable?▼

An unreachable rs_dev MCP surface usually means the plugin was installed or updated mid-session, so MCP servers never registered. Run /reload-plugins or start a new session; if that is ruled out, the daemon is down and must be repaired with /redskilled.

When should I not use /go for a coding request?▼

Avoid /go for work that is or should be a tracked GitHub issue (use /afk), conversational steering (use /goal), batches of related work (author a Spec then /afk), urgent queue jumps (use priority:urgent labels), or hand-done branches needing only landing (use /retake).