watch-merges
Watch one feature's PR in the background and auto-clean its agent, worktree, and branch once it merges. Use after a feature's PR is open to wire hands-off cleanup on merge (typically called by /hv:build-feature as its final step). It polls GitHub with exponential backoff and only triggers cleanup — the actual removal is done by /hv:clean-agents.
What this skill does
# Watch merges → auto-clean
A **thin watcher**. It polls one PR until it merges, then runs
**`/hv:clean-agents`**, which delegates the actual removal to the `janitor`
subagent. All cleanup guardrails live there — this skill never deletes anything
itself.
## Input
$ARGUMENTS
`<pr|branch>` — the feature PR to watch (typically passed by `/hv:build-feature`
as its final step, right after opening the PR). Optional tuning:
`--initial S` (first poll gap, default 30s), `--factor N` (backoff multiplier,
default 2), `--cap S` (max gap, default 600s), `--max H` (give up after H hours,
default 24).
## Step 1 — Launch the background watcher
Poll the PR in the **background** so no live session is tied to the wait. The
bundled script backs off exponentially — quick polls right after the PR opens,
when a merge is most likely imminent, widening to `--cap` for the long tail —
and stops on merge, close, or the `--max` deadline:
```bash
bash "${CLAUDE_PLUGIN_ROOT}/scripts/watch-merge.sh" <pr|branch>
```
Run it with **Bash's background mode** so it keeps polling across turns and
re-invokes you when it exits. Its final stdout line is one of:
- `MERGED <branch>` → go to Step 2 and clean.
- `CLOSED_UNMERGED <branch>` → the PR was closed without merging; **clean
nothing** (never destroy unmerged work) — just report it.
- `TIMEOUT <branch>` → still open after `--max`; report that it's still
open and suggest re-running `/hv:watch-merges <pr>` (or cleaning manually once
it lands).
- `ERROR <message>` → bad target or `gh` not authenticated; surface it.
## Step 2 — On merge, hand off to clean-agents
When (and only when) the watcher reports `MERGED`, run:
```
/hv:clean-agents <branch>
```
## Guardrail
Cleanup only ever runs through `/hv:clean-agents` → `janitor`, which **re-checks
that the agent is not still running and the PR is merged** before removing
anything. This skill watches and triggers; it never deletes resources itself.
result: watched <pr|branch> → <merged: cleaned | closed-unmerged: skipped | timeout: still open>.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.