swarm-checkpointlisted

# /swarm-checkpoint — Validate and commit progress Use this skill to checkpoint your work mid-task. It runs the project's validation suite, and based on the result either commits cleanly OR reports a blocker without committing. ## Workflow ### Step 1 — Run validation Invoke the project's pre-commit validation via the `/check` slash command. This runs format + lint + tests. ALL must pass with zero warnings. If `/check` is not available in this project, run the equivalent: format + lint + test suite as defined in `CLAUDE.md` or the project manifest (`pyproject.toml`, `package.json`, `Makefile`, etc.). ### Step 2A — On PASS 1. Call `mcp__swarm__swarm_report_progress` with `phase="checkpointing"` and a reasonable percent estimate based on overall task progress. 2. Run `git status --short` and `git diff --stat` to identify exactly which files you intentionally changed. 3. Stage **only** the files you changed for this checkpoint, by name. **NEVER use `git add -A` or `git add .`** — that risks committing unintended files (`.env`, build artifacts, sibling work). 4. Generate a concise commit message following the project's conventions. Use the project's `/commit` slash command if present; otherwise commit manually with a HEREDOC body following Conventional Commits unless `CLAUDE.md` says otherwise. 5. Make the commit. Do **NOT** push unless the user has explicitly asked you to. 6. Report a one-line confirmation, e.g. `Checkpoint committed: <short hash> "<subject>".` ### Step 2