doey-kill-window

Terminate a Doey team window and clean up its runtime state.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kill a Doey team window — stop all related processes, teardown the tmux window, and remove runtime state to reclaim resources and restore a clean workspace.

Core Features & Use Cases

  • Stop all processes in the target window and terminate its session safely.
  • Remove the tmux window from the session and clean up runtime artifacts, including optional worktree teardown.
  • Use this when a window becomes unresponsive or misbehaving to reset the environment without disrupting other windows.

Quick Start

Terminate the specified Doey window and clean up its runtime state.

Frequently Asked Questions about doey-kill-window

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

FAQPage Schema
How do I kill a tmux window and clean up unresponsive processes safely?

To kill a tmux window and clean up processes safely, stop all related processes, teardown the session, and remove runtime artifacts. This ensures safe teardown of processes and tmux windows to reclaim resources and restore a clean workspace without data loss.

What is the best way to reset a misbehaving tmux session without disrupting other windows?

The best way to reset a misbehaving tmux session is to terminate the specific Doey team window and clean up its runtime state. This enables safe teardown of unresponsive processes and runtime artifacts while leaving other windows completely unaffected.

Does process termination for tmux windows include optional worktree cleanup?

Yes, process termination for tmux windows includes optional worktree teardown. This removes runtime artifacts across local or remote sessions, implementing explicit validation and safe process termination to minimize data loss and ensure repeatable resets.

Can I use this teardown approach for remote sessions and local runtime cleanup?

Yes, you can use this teardown approach for both remote sessions and local runtime cleanup. It safely terminates processes, removes tmux windows, and cleans up runtime artifacts across local or remote sessions to reclaim resources effectively.

Why does explicit validation matter when terminating unresponsive tmux windows?

Explicit validation matters when terminating unresponsive tmux windows because it ensures safe process termination and minimizes data loss. By validating before teardown, you guarantee repeatable resets and prevent the accidental destruction of active runtime artifacts.