Menu
Stop a running Ratchet pipeline.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Collect Ratchet local pipeline debug evidence. Use when a run is failed, stuck, stale, stopped, missing outputs, has confusing LLM behavior, or needs local evidence from pipeline traces, events.jsonl, worker.log, raw LLM artifacts, and a debug bundle directory.
Show local Ratchet setup status and optional host-agent configuration.
Evaluate and enhance a ratchet skill using LLM-as-judge A/B testing with an iterative improvement loop.
Run the Ratchet skill extraction pipeline to analyze project sessions and generate reusable skills and strategies.
Show Ratchet help — available commands, output locations, skill and strategy structure, and usage tips.
View or update your Ratchet developer profile (language, level, style) to personalise skill extraction.
| name | ratchet-stop |
| description | Stop a running Ratchet pipeline. |
| argument-hint | [run-id] |
| allowed-tools | Bash, Read, AskUserQuestion |
Stop a currently running Ratchet skill extraction pipeline.
RATCHET_DIR="${RATCHET_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-$(cat ~/.local/ratchet/plugin-root 2>/dev/null)}}}"
set -a && . "$RATCHET_DIR/.env" 2>/dev/null && set +a
uv run --directory "$RATCHET_DIR" python -m ratchet.client.check_auth
If the auth check fails (non-zero exit), show the output to the user and stop.
Skip to the Stop step below using the provided run-id.
Step 1 — List active runs:
uv run --directory "$RATCHET_DIR" ratchet pipeline-status
If the output says "No active pipeline runs.", tell the user and stop.
Step 2 — Ask user to confirm:
Use the AskUserQuestion tool to present the active runs and let the user choose.
Always include a cancel option — even if there is only one active run.
Format the question like:
Active pipeline runs:
1. {run_id} | project: {project_id} | status: {status}
Phase: {current_phase} ({sessions_processed}/{sessions_total})
Which run would you like to stop? Select a number, or 0 to cancel.
If user selects 0 or cancels, say "Cancelled." and stop.
uv run --directory "$RATCHET_DIR" ratchet pipeline-stop --run-id <SELECTED_RUN_ID>
Report the result to the user. If successful, confirm: "Pipeline {run_id} has been stopped."
Then show where to inspect the preserved stop event and worker log:
uv run --directory "$RATCHET_DIR" ratchet pipeline-inspect --run-id <SELECTED_RUN_ID>
uv run --directory "$RATCHET_DIR" ratchet pipeline-logs --run-id <SELECTED_RUN_ID> --tail 80