skills.rest
SpecterShell
SpecterShellCOMMUNITY
Explore all skills by this author →
GitHub

axrepl-kill

Terminate axrepl REPL sessions by name, UUID, or all via CLI.

Updated Mar 20, 2026
Search Tags:#automation#bash#repl#session#kill#daemon#axrepl
One-click install
npx skills add https://github.com/SpecterShell/axec --skill axrepl-kill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: axrepl-kill
Source: https://github.com/SpecterShell/axec/tree/main/skills/axrepl-kill
Command: npx skills add https://github.com/SpecterShell/axec --skill axrepl-kill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Terminating a running axrepl REPL session or all REPL sessions can be error-prone and time-consuming when sessions linger or consume resources.

Core Features & Use Cases

  • Terminate a specific REPL session by name or UUID
  • Kill all active REPL sessions managed by the axrepl daemon
  • Clear feedback and safe, explicit control with error handling for failed terminations

Quick Start

Terminate a specific session with axrepl kill --session NAME or all sessions with axrepl kill --all.

Frequently Asked Questions about axrepl-kill

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

FAQPage Schema
How do I force-terminate a single axrepl REPL session by name?▼

You can force-terminate a specific axrepl REPL session by running axrepl kill --session NAME. This targets one active session managed by the daemon for explicit closure.

What is the best way to kill all active REPL sessions managed by the daemon?▼

Use axrepl kill --all to terminate every active REPL session managed by the axrepl daemon. This performs a bulk cleanup of all lingering sessions.

Can I get structured output when terminating REPL sessions?▼

Yes, pass the --json flag to the kill command to receive structured output. This ensures clear feedback and safe, explicit control over session termination.

Why do I need to explicitly kill sessions instead of letting them timeout?▼

Lingering REPL sessions can be error-prone and consume system resources unnecessarily. Explicitly killing them ensures safe termination and immediate resource cleanup.

Does the kill command support targeting sessions by UUID?▼

Yes, you can apply the termination to individual sessions by either name or UUID. This allows precise targeting of specific REPL instances.

What happens if a session termination fails during bulk cleanup?▼

The command includes error handling for failed terminations, providing clear feedback during bulk cleanup. This ensures safe and explicit control over the process.

Related Skills

Explore More Software Engineering Skills→
SpecterShellSpecterShell

axrepl-run

Manage persistent Python, Node, Bash, and Zsh REPL sessions in a daemon-backed environment.

Community
Intermediate
bbugyi200bbugyi200
5

sase_agents_status

Query and manage SASE background agent lifecycle via sase CLI JSON output.

Community
Intermediate
SpecterShellSpecterShell

axrepl-clean

Remove exited axrepl REPL sessions and their on-disk state.

Community
Basic
tankygranny05tankygranny05
2

ram-consumption-verification

Measure system memory before and after terminating processes with htop in tmux.

Community
Intermediate