doey-kill-all-sessions

Terminate all doey tmux sessions and clean up /tmp/doey/* runtime files.

6|2|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/FRIKKern/doey --skill doey-kill-all-sessions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doey-kill-all-sessions
Source: https://github.com/FRIKKern/doey/tree/main/.claude/skills/doey-kill-all-sessions
Command: npx skills add https://github.com/FRIKKern/doey --skill doey-kill-all-sessions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Doey users need a reliable way to terminate all Doey tmux sessions and clean up runtime artifacts to recover a clean environment after experiments, crashes, or shutdowns.

Core Features & Use Cases

  • Comprehensive shutdown: terminates all doey tmux sessions and their child processes to prevent orphaned tasks.
  • Runtime cleanup: removes /tmp/doey/* runtime files to free resources and reduce clutter.
  • Safe confirmation: includes an explicit confirmation prompt to prevent accidental data loss or unintended terminations.

Quick Start

Execute this skill to terminate all Doey tmux sessions and purge runtime files.

Frequently Asked Questions about doey-kill-all-sessions

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

FAQPage Schema
How do I kill all lingering tmux sessions and clean up runtime files?

To kill lingering tmux sessions and clean up runtime files, you need to terminate all associated processes and remove the /tmp/doey/* directory. This ensures a clean environment recovery.

What is the safest way to terminate all Doey tmux sessions without losing data?

The safest way to terminate Doey tmux sessions involves using an explicit confirmation prompt before killing processes. This prevents accidental data loss by verifying intent.

How do I remove orphaned processes and /tmp/doey/* runtime artifacts after a crash?

Removing orphaned processes and /tmp/doey/* runtime artifacts requires terminating all doey tmux child processes and purging the runtime files. This frees resources and reduces clutter.

Does killing Doey tmux sessions affect other system resources or non-Doey processes?

Killing Doey tmux sessions does not affect other system resources. The process strictly targets Doey shutdowns and associated child processes, leaving non-Doey operations untouched.

When should I perform a Doey runtime cleanup and session termination?

You should perform a Doey runtime cleanup and session termination during maintenance, recovery, or after experiments. This handles lingering tmux sessions and clears /tmp/doey/* files.