/heartbeat
Run a WoterClip heartbeat cycle (pick up issues, do work, report)
$ npx -y skills add wotai-dev/woterclip --agent claude-codeShips with woterclip. Installing the plugin gets this command.
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/heartbeat
Context preview
What this command does when you run it.
Run a WoterClip heartbeat cycle (pick up issues, do work, report)
Command definition
heartbeat.mddescription: Run a WoterClip heartbeat cycle (pick up issues, do work, report) argument-hint: "[--dry-run] [--persona NAME]"
Run the WoterClip heartbeat using the heartbeat skill.
Arguments passed: $ARGUMENTS
Parse the arguments:
- If `--dry-run` is present, pass it through to the heartbeat procedure (step 3 reports what would be picked without doing work)
- If `--persona <name>` is present, filter to only issues matching that persona's label
Execute the full 11-step heartbeat procedure. On any error or exit, apply the ownership rule to the lockfile at `.woterclip/.heartbeat-lock`: delete it only if it still carries this beat's `beat_id`. If it is missing or carries another id, a later beat re-took it — leave it alone.
GitHub Issues-backed agent orchestration for Claude Code. A single Claude instance wears different "hats" (personas) based on GitHub issue labels – an Orchestrator routes work, a CEO makes strategic calls, and worker personas execute.