Cancel active OMX modes with dependency-aware sequencing and safety checks.
npx skills add https://github.com/RJJJJ/project2 --skill cancel-rjjjj
Please help me install this Agent Skill. Skill: cancel Source: https://github.com/RJJJJ/project2/tree/main/.codex/skills/cancel Command: npx skills add https://github.com/RJJJJ/project2 --skill cancel-rjjjj
The Cancel Skill provides a safe, centralized way to terminate any active OMX mode and perform comprehensive cleanup, preventing lingering state and inconsistent behavior.
Invoke /cancel to terminate any active OMX mode and perform safe state cleanup.
High-intent search queries and answers about installing and using this skill.
To cancel an active OMX mode, invoke a centralized cancellation command that detects active modes across sessions and applies dependency-aware sequencing to restore a clean, non-conflicting state.
Terminating multiple OMX modes requires handling them in a specific dependency order—autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, and team—to ensure safety checks prevent inconsistent behavior.
Yes, you can use forceful cleanup to remove legacy state artifacts and ensure a fresh start, while the process preserves resume data where applicable during the session state-management cancellation.
Dependency-aware sequencing is required for OMX session cancellation because active modes like swarm, ultrapilot, pipeline, and team have interdependencies, and enforcing safety checks prevents lingering state and conflicts.
If OMX mode cancellation leaves lingering tmux state, apply force cleanup to remove legacy state artifacts across sessions, which enforces a fresh start and prevents inconsistent behavior from the terminated modes.
eszxcvfdCancel active OMX modes and clean up session state.
OliverOuyangCancel active OMC modes and restore a clean state.
JaCha00Cancel active OMX modes and clean up session state.
oneforceCancel active OMC modes and clean session state artifacts.
