skills.rest
JaCha00
JaCha00COMMUNITY
Explore all skills by this author →
GitHub

cancel

Cancel active OMX modes and clean up session state.

Updated Jul 2, 2026
Search Tags:#state management#cleanup#cancel#omx#system operations
One-click install
npx skills add https://github.com/JaCha00/nais2-integration-complete --skill cancel-jacha00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/JaCha00/nais2-integration-complete/tree/main/.codex/skills/cancel
Command: npx skills add https://github.com/JaCha00/nais2-integration-complete --skill cancel-jacha00

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires state management tools, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of canceling active OMX modes and cleaning up their state, ensuring a smooth exit from ongoing operations.

Core Features & Use Cases

  • Cancel OMX Modes: Detects and terminates active OMX modes like autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, and team.
  • Session-Aware State Management: Handles session-scoped cleanup and legacy state removal.
  • Force Mode: Clears all state files and legacy artifacts for a complete reset.
  • Team Mode Cleanup: Gracefully shuts down and cleans up team mode with force-kill fallback.
  • Structured Reports: Provides detailed reports on cancellation progress and state cleanup.

Quick Start

Cancel the active OMX mode by running the cancel skill with the command: /cancel

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I cancel active OMX modes and clean up their state?▼

To cancel active OMX modes and clean up state, run the cancel skill with the /cancel command. It terminates workflows like autopilot, ultrawork, and pipeline while removing session-scoped state files.

What OMX workflows can be terminated using session-aware state cleanup?▼

Session-aware state cleanup terminates OMX workflows including autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, and team, ensuring all legacy artifacts are gracefully removed.

Do I need state management tools to cancel OMX workflows?▼

Yes, you need state management tools and valid session identifiers to cancel OMX workflows. These dependencies allow the cancellation process to accurately detect active modes and scope the cleanup correctly.

How does force mode reset OMX state differently than standard cleanup?▼

Force mode resets OMX state by clearing all state files and legacy artifacts for a complete reset, whereas standard cleanup only handles session-scoped state removal for a smooth exit.

What happens if team mode does not shut down gracefully during OMX cancellation?▼

If team mode does not shut down gracefully during OMX cancellation, the process uses a force-kill fallback to terminate the workflow and ensures all associated state files are fully cleaned up.

Related Skills

Explore More Software Engineering Skills→
BetaSBetaS

cancel

Detect and terminate active OMX modes with session-aware state cleanup.

Community
Advanced
tuandzungtuandzung

cancel

Detect and terminate active OMX modes with state cleanup.

Community
Advanced
wmasfoewmasfoe

cancel

Cancel active OMX modes across sessions with dependency-aware state cleanup.

Community
Advanced
YeaChan05YeaChan05

cancel

Cancel active OMX modes and emit a structured cancel report.

Community
Advanced