Auto-invokedCommand
Automation
/woterclip-init
Initialize WoterClip in this repo (config, personas, GitHub labels)
Install
> /plugin marketplace add wotai-dev/woterclip > /plugin install woterclip@woterclip
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
/woterclip-init
Context preview
What this command does when you run it.
Initialize WoterClip in this repo (config, personas, GitHub labels)
Command definition
woterclip-init.mddescription: Initialize WoterClip in this repo (config, personas, GitHub labels)
Initialize WoterClip in this repository using the woterclip-init skill.
Follow the full initialization procedure from the skill: 1. Verify the `gh` CLI is installed and authenticated (`gh auth status`) 2. Gather GitHub context (repo, user login) 3. Ask which persona preset to scaffold 4. Create GitHub labels (state + persona labels) 5. Scaffold `.woterclip/` with config and persona templates from `${CLAUDE_PLUGIN_ROOT}/templates/` 6. Offer schedule setup 7. Print summary of what was created
If `.woterclip/` already exists, check the existing config's `version` FIRST: a `version: 1` (Linear-era) config runs the v1→v2 migration from the skill's Re-initialization section before anything else. Only then ask whether to overwrite, merge, or cancel.
Ships withwoterclip
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.
Get the whole plugin, auto-invoked
Other commands on woterclip.
Auto-invokedCommand