doey-kill-session

Terminate all tmux windows, processes, and runtime files of a Doey session.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kill the entire Doey session — all windows, processes, and runtime files. Use when you need to "kill this session", "shut down doey", or "stop everything and clean up".

Core Features & Use Cases

  • Terminate all tmux windows and panes for the active Doey session to ensure a clean shutdown.
  • Remove runtime state to allow a fresh start on re-init.
  • Safe-guarded with explicit confirmation to prevent accidental closures in active work.
  • Use Case: If Doey becomes unresponsive or you need to reset the environment to recover from a failed run.

Quick Start

Confirm the prompt to kill the Doey session and remove runtime state, then re-init with doey.

Frequently Asked Questions about doey-kill-session

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

FAQPage Schema
How do I kill a tmux session and clean up all runtime data at once?

To kill a tmux session and clean up runtime data, this Skill terminates all active windows and panes, safely signals related processes, and removes runtime artifacts after explicit confirmation. This ensures a completely fresh start for re-initialization.

How do I shut down an unresponsive Doey deployment safely?

To shut down an unresponsive Doey deployment, you need to terminate the entire session across all tmux windows. This Skill inspects the active session, safely signals processes to stop, and removes leftover runtime state to allow recovery.

What is the best way to reset my tmux environment for a fresh start?

The best way to reset your tmux environment is to kill the entire session and remove all associated runtime files. This complete reset prevents conflicts from leftover state and allows you to cleanly re-init your deployment.

Does killing the Doey session require explicit confirmation?

Yes, killing the Doey session requires explicit confirmation. This safeguard prevents accidental closures of active work, ensuring you only terminate tmux windows, processes, and runtime artifacts when you intentionally request a full shutdown.

Why does my Doey environment need a complete reset after a failed run?

A complete reset is needed after a failed run to remove corrupted runtime state. Terminating all tmux windows and cleaning up runtime artifacts ensures no residual processes or files interfere when you re-init the Doey session.