GGPrompts

worker-done

@GGPrompts/worker-done
GGPrompts
116
10 forks
Updated 1/6/2026
View on GitHub

Complete worker task: verify build, run code review, commit, and close issue. Invoke with /conductor:worker-done <issue-id>

Installation

$skills install @GGPrompts/worker-done
Claude Code
Cursor
Copilot
Codex
Antigravity

Details

Pathplugins/conductor/skills/worker-done/SKILL.md
Branchmain
Scoped Name@GGPrompts/worker-done

Usage

After installing, this skill will be available to your AI coding assistant.

Verify installation:

skills list

Skill Instructions


name: worker-done description: "Complete worker task: verify build, run code review, commit, and close issue. Invoke with /conductor:worker-done <issue-id>"

Worker Done - Task Completion Orchestrator

Orchestrates the full task completion pipeline by composing atomic commands.

Usage

/conductor:worker-done TabzChrome-abc

# Or if issue ID is in your task header:
/conductor:worker-done

Pipeline Overview

StepCommandBlocking?
1/conductor:verify-buildYes - stop on failure
2/conductor:run-testsYes - stop on failure
3/conductor:code-reviewYes - stop on failure
4/conductor:commit-changesYes - stop on failure
5/conductor:create-followupsNo - log and continue
6/conductor:update-docsNo - log and continue
7/conductor:close-issueYes - report result

Execute Pipeline

Step 1: Verify Build

echo "=== Step 1: Build Verification ==="

Run /conductor:verify-build. If passed: false -> STOP, fix errors, re-run.

Step 2: Run Tests

echo "=== Step 2: Test Verification ==="

Run /conductor:run-tests. If passed: false -> STOP, fix tests, re-run.

Step 3: Code Review

echo "=== Step 3: Code Review ==="

Run /conductor:code-review (spawns code-reviewer subagent). If passed: false -> STOP, fix blockers, re-run.

Step 4: Commit Changes

echo "=== Step 4: Commit ==="

Run /conductor:commit-changes <issue-id>. Creates conventional commit with Claude signature.

Step 5-6: Non-blocking

echo "=== Step 5: Follow-up Tasks ==="
echo "=== Step 6: Documentation Check ==="

Run /conductor:create-followups and /conductor:update-docs. Log and continue.

Step 7: Close Issue

echo "=== Step 7: Close Issue ==="

Run /conductor:close-issue <issue-id>. Reports final status.


Atomic Commands Reference

CommandDescription
/conductor:verify-buildRun build, report errors
/conductor:run-testsRun tests if available
/conductor:code-reviewOpus review with auto-fix
/conductor:codex-reviewCodex review (read-only, cheaper)
/conductor:commit-changesStage + commit with conventional format
/conductor:create-followupsCreate follow-up beads issues
/conductor:update-docsCheck/update documentation
/conductor:close-issueClose beads issue

Custom Pipelines

Compose commands for custom workflows:

Quick commit (skip review):

/conductor:verify-build
/conductor:run-tests
/conductor:commit-changes
/conductor:close-issue <id>

Review-focused (no commit):

/conductor:verify-build
/conductor:code-review

Error Handling

StepOn Failure
BuildShow errors, stop pipeline
TestsShow failures, stop pipeline
ReviewShow blockers, stop pipeline
CommitShow git errors, stop pipeline
Follow-upsNon-blocking - log and continue
DocsNon-blocking - log and continue
CloseShow beads errors

Re-running After Fixes

If the pipeline stopped:

  1. Fix the issues
  2. Run /conductor:worker-done again

The pipeline is idempotent - safe to re-run.


After Completion

When /conductor:worker-done succeeds:

  • Issue is closed in beads
  • Commit is on the feature branch
  • Worker's job is done

The conductor is responsible for:

  • Merging the feature branch to main
  • Killing this worker's tmux session
  • Removing the worktree
  • Deleting the feature branch

Workers do NOT kill their own session - the conductor monitors for closed issues and handles cleanup.


Reference Files

FileContent
references/example-sessions.mdExample output for different scenarios

Execute this pipeline now.