cancel

Cancel active OMC modes by detecting sessions and executing cleanup scripts.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Moliboy5000/.claude --skill cancel-moliboy5000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/Moliboy5000/.claude/tree/main/plugins/cache/omc/oh-my-claudecode/4.8.2/skills/cancel
Command: npx skills add https://github.com/Moliboy5000/.claude --skill cancel-moliboy5000

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a robust and intelligent way to stop any currently running "Oh My Claude Code" (OMC) mode, ensuring that processes are terminated gracefully and state is cleaned up appropriately.

Core Features & Use Cases

  • Intelligent Mode Detection: Automatically identifies which OMC mode (e.g., Autopilot, Ralph, Team) is active.
  • Graceful Shutdown: Executes specific cleanup procedures for each mode, preserving progress where possible (like Autopilot).
  • Forceful Cleanup: Offers a --force or --all option to clear all active sessions and legacy artifacts when a clean slate is needed.
  • Use Case: You've started a complex automated workflow with Autopilot, but need to stop it immediately to address an urgent issue. Using the cancel skill ensures Autopilot stops cleanly, and you can resume later.

Quick Start

Use the cancel skill to stop the currently active OMC mode.

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I stop an active OMC mode safely without losing workflow progress?

To stop an active OMC mode safely, the cancel skill detects the current session and executes mode-specific cleanup scripts, ensuring processes like Autopilot terminate gracefully while preserving progress for later resumption.

How does graceful shutdown work for automated workflows like Autopilot and Ralph?

Graceful shutdown works by identifying the active OMC mode and running targeted cleanup procedures. It manages dependencies between modes like Autopilot, Ralph, and Ultrawork during cancellation to terminate sessions cleanly.

Can I force clear all OMC session and legacy state files for a clean slate?

Yes, you can force clear all OMC session files by using the forceful cleanup option, which clears all active sessions and legacy artifacts when you need a completely clean slate.

What's the best way to cancel a Team or Autopilot session during an urgent interruption?

The best way to cancel a Team or Autopilot session during an interruption is using the cancel skill, which stops the automated workflow immediately and executes the specific cleanup procedures for that mode.

Why do dependencies between OMC modes matter when stopping a workflow?

Dependencies between OMC modes matter because modes like Autopilot, Ralph, and Ultrawork interact during cancellation. The cancel skill manages these dependencies to prevent broken sessions or incomplete state cleanup.

When should I use forceful cleanup instead of graceful shutdown for OMC modes?

You should use forceful cleanup instead of graceful shutdown when you need a clean slate and do not intend to resume progress, as it clears all active sessions and legacy state files without preserving workflow data.