cancel

Cancel active OMG modes and clean up their state.

153|12|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/jmstar85/oh-my-githubcopilot --skill cancel-jmstar85
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/jmstar85/oh-my-githubcopilot/tree/main/.github/skills/cancel
Command: npx skills add https://github.com/jmstar85/oh-my-githubcopilot --skill cancel-jmstar85

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cancel active OMG modes and clean up associated state to prevent partial runs and ensure a clean slate for a restart.

Core Features & Use Cases

  • Auto-detects the currently active OMG mode (Autopilot, Ralph, Ultrawork, UltraQA, Team, Self-Improve) and initiates a safe shutdown.
  • Supports forceful shutdown with --force/--all to clear all state in one go.
  • Preserves or resets mode-specific state as appropriate, enabling safe resume or clean termination of workflows.

Quick Start

Cancel the currently active OMG mode by issuing the /cancel command or use --force to clear all states and shut everything down.

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I safely stop a running multi-agent workflow and clean up its state?

You can cancel an active OMG mode to safely stop a multi-agent workflow and clean up its state. This clears the active run and ensures a clean slate for future orchestration tasks.

What is the best way to forcefully shut down all active automation modes?

The best way to forcefully shut down all active automation modes is by using the cancel command with the --force or --all flag. This clears all state in one go, bypassing selective preservation.

Does the cancel command preserve workflow state for later resumption?

Yes, the cancel command preserves or resets mode-specific state as appropriate during shutdown. This enables safe resumption or clean termination of workflows depending on the active mode.

How does the system detect which automation mode to shut down?

The system detects the active automation mode to shut down by reading the configuration stored in the .omg/state/ directory. It then initiates the appropriate cleanup or preservation logic for that specific mode.

Can I use selective shutdown to stop specific orchestration tasks without clearing everything?

Yes, you can use selective shutdown to stop specific orchestration tasks. The cancel command auto-detects the active mode and performs the appropriate cleanup or preservation without needing a full forceful clearing.