Skip to content
Back to skills

2528 Zerg Stop 35f9bae6

ASecurity

Stop ZERG workers gracefully or forcefully.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
toolsbash

Works with

  • claude code

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 2528-zerg-stop_35f9bae6 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 2528 Zerg Stop 35f9bae6?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 2528 Zerg Stop 35f9bae6
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-2528-zerg-stop-35f9bae6/badge)](https://www.skillsdirectory.com/skills/tools-only-2528-zerg-stop-35f9bae6)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
# /zerg:stop

Stop ZERG workers gracefully or forcefully.

## Synopsis

```
/zerg:stop [OPTIONS]
```

## Description

`/zerg:stop` halts running ZERG workers. By default it performs a graceful shutdown that allows workers to checkpoint their progress. With `--force`, it terminates workers immediately.

### Graceful Stop (Default)

1. Sends a checkpoint signal to all active workers.
2. Workers create a WIP (work-in-progress) commit with their current changes.
3. Workers update state with checkpoint information.
4. Containers stop cleanly.
5. State is preserved for later resume with `/zerg:rush --resume`.

In-progress tasks are annotated with `PAUSED` in the Claude Code Task system.

### Force Stop

1. Immediately terminates worker containers.
2. No WIP commits are made.
3. In-progress tasks are marked as failed.
4. Uncommitted work may be lost.

In-progress tasks are annotated with `FORCE STOPPED` in the Claude Code Task system.

### WIP Commit Format

When stopped gracefully, each worker creates a commit with this format:

```
WIP: ZERG [worker-<id>] checkpoint during <task_id>

Status: <percentage>% complete
Files modified:
  - path/to/file.py (added)

Worker-ID: <id>
Feature: <feature>
Context-Usage: <percentage>%
```

### State After Stop

| Component | Graceful | Force |
|-----------|----------|-------|
| Containers | Stopped cleanly | Killed |
| Worktrees | Preserved | Preserved |
| State file | Updated | May be stale |
| Current tasks | PAUSED | FAILED |
| WIP changes | Committed | Lost |

## Options

| Option | Description |
|--------|-------------|
| `-f`, `--feature TEXT` | Feature to stop (auto-detected from `.gsd/.current-feature`) |
| `-w`, `--worker INTEGER` | Stop only a specific worker by ID |
| `--force` | Force immediate termination without checkpointing |
| `--timeout INTEGER` | Graceful shutdown timeout in seconds (default: 30) |

## Examples

```bash
# Graceful stop of all workers
/zerg:stop

# Force stop all workers immediately
/zerg:stop --force

# Stop only worker 2
/zerg:stop --worker 2

# Force stop a specific worker
/zerg:stop --worker 3 --force

# Graceful stop with extended timeout
/zerg:stop --timeout 60

# Quick timeout
/zerg:stop --timeout 10
```

## Recovery After Stop

```bash
# Resume execution from checkpoint
/zerg:rush --resume

# Resume with a different worker count
/zerg:rush --resume --workers 3

# Check what was in progress
/zerg:status

# View errors before resuming
/zerg:logs --level error

# Retry failed tasks
/zerg:retry --all-failed
```

## See Also

- [[zerg-rush]] -- Resume execution after stopping
- [[zerg-status]] -- Check state after stop
- [[zerg-retry]] -- Re-run tasks that failed during stop
- [[zerg-logs]] -- Inspect worker logs for issues
- [[zerg-Reference]] -- Full command index

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…