skills.rest
xz1220
xz1220COMMUNITY
Explore all skills by this author →
𝕏@xngzhng118250GitHub

cancel

Cancel active oh-my-kimi workflow modes with scoped cleanup and termination.

2|Updated May 11, 2026
Search Tags:#state cleanup#session-aware#workflow cancellation#tmux team shutdown#ralph stop#autopilot abort
One-click install
npx skills add https://github.com/xz1220/oh-my-kimi --skill cancel-xz1220
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/xz1220/oh-my-kimi/tree/main
Command: npx skills add https://github.com/xz1220/oh-my-kimi --skill cancel-xz1220

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill cancels any active oh-my-kimi mode (such as autopilot, ralph, team, ultrawork, and related loops) and performs the required cleanup so you can return to a clean, controllable state.

Core Features & Use Cases

  • Mode-aware cancellation: Detects which oh-my-kimi workflow(s) are active and cancels them in the correct dependency order.
  • Safe scoped cleanup: Prefers session-scoped cleanup (when session_id is available) and only falls back to legacy/global cleanup when needed.
  • Force & all-clear options: Supports --force / --all to aggressively clear persistent artifacts (including leftovers) when graceful cancellation is blocked.
  • Ralph dependency handling: Ensures linked modes are terminalized (e.g., setting cancelled phases and completed_at) rather than silently deleting state.
  • Team(tmux) termination: Gracefully signals team workers first, then force-kills remaining tmux panes and clears team state.

Quick Start

Run: /cancel

Frequently Asked Questions about cancel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop an oh-my-kimi autopilot or ralph workflow safely?▼

To stop an oh-my-kimi autopilot or ralph workflow safely, run /cancel to detect active session-scoped state and apply mode-specific termination, ensuring linked executions are terminalized with cancelled phases and completed_at timestamps.

What is the best way to clean up tmux team workers after cancelling a workflow?▼

The best way to clean up tmux team workers is using mode-aware cancellation that gracefully signals team workers first, then force-kills remaining tmux panes and clears team state to return to a clean, controllable environment.

How does session-aware workflow cancellation preserve resume behavior?▼

Session-aware workflow cancellation preserves resume behavior by detecting current session-scoped state and applying mode-specific termination that sets terminal phases and completed_at fields, rather than silently deleting or corrupting the state.

Can I forcefully clear persistent workflow artifacts when graceful cancellation is blocked?▼

Yes, you can forcefully clear persistent workflow artifacts when graceful cancellation is blocked by using the --force or --all options to aggressively clear leftovers and perform global cleanup.

Why does ralph dependency handling require terminalizing linked modes instead of deleting state?▼

Ralph dependency handling requires terminalizing linked modes to enforce correct cancellation post-conditions, ensuring cancelled phases and completed_at timestamps are set properly so resume behavior remains intact for appropriate modes.

Related Skills

Explore More Software Engineering Skills→
sigridjinethsigridjineth
20

cancel

Detect and shut down active oh-my-codex modes with cleanup routines.

Community
Advanced
aresbitaresbit
46

tmux

Control tmux sessions and capture pane output remotely.

Community
Advanced
realsigridjinrealsigridjin
20

cancel

Cancel active oh-my-codex orchestration modes and clean up runtime state.

Community
Advanced
xz1220xz1220

debug

Diagnose Kimi CLI workflow failures using trace and state evidence.

Community
Intermediate