Menü
Interactive /gobby qa launcher. Dispatches the shared qa-reviewer agent for a task.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | qa |
| description | Interactive /gobby qa launcher. Dispatches the shared qa-reviewer agent for a task. |
| version | 1.0.0 |
| category | core |
| triggers | qa, gobby qa, qa reviewer, review task |
| metadata | {"gobby":{"audience":"interactive","depth":0}} |
Use this skill when the user invokes /gobby qa to run the same read-only
QA reviewer that lifecycle dispatch uses, independent of gobby build.
The workflow definition is src/gobby/install/shared/workflows/qa.yaml.
Resolve a task ref before dispatch. Accept #N, a numeric ref, or a dotted
task path. If the user does not provide one, ask for the task ref.
Ask for the I/D mode unless it is already clear from the user's request:
I) Interactive - dispatch qa-reviewer and surface the run ids.
D) Delegated - dispatch qa-reviewer and end the turn.
Persist the choice as value="interactive" | "delegated" for the handoff.
Both modes use the qa-reviewer agent and the shared workflow YAML.
The QA loop is read-only. The qa-reviewer checks the diff, runs focused
validation, and emits exactly one verdict:
approve_review(stage_name="development")reject_review(stage_name="development")escalate_taskFor tasks marked tdd:required or requesting test-driven-development, the
reviewer must reject unless red, green, refactor/final-green, exact test command,
and test-quality audit evidence are present.
Use the explicit user-facing summary approve / reject / escalate when
describing possible outcomes.
Run the qa workflow with the resolved task id:
call_tool("gobby-workflows", "run_pipeline", {
"name": "qa",
"inputs": {
"task_id": "<task_ref>",
"mode": "<interactive|delegated>"
}
})
Surface the returned execution id. The spawned qa-reviewer owns the verdict;
this skill does not edit files, commit, approve, reject, or escalate itself.
close_task; the lifecycle dispatcher owns closure.qa-reviewer agent instructions here.Instructions for using gcode CLI for code search and retrieval. Loaded on demand when project has a code index.
Pre-transition checklist for closing or reviewing tasks. Covers fresh verification evidence, commits, and memory gates.
Use when processing CodeRabbit review comments, CodeRabbit CLI reports, or `$gobby coderabbit [findings]` requests.
Use when creating, editing, or validating Gobby skills, especially when a skill must change agent behavior or become discoverable through gobby-skills.
Use when coordinating a full gobby build run for an epic or task, especially when the user assigns the current session as coordinator, asks for a coordination epic, wants build agents/worktrees monitored, or wants gobby build bugs fixed so future runs work unattended.
Router contract for provider-aware Gobby help and installed skill dispatch.