kawa-clean

Terminate Kawa and simplex-chat processes and remove temporary directories via npm run clean.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/dentedgem9846-claw/chronocrystal-opsx --skill kawa-clean
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kawa-clean
Source: https://github.com/dentedgem9846-claw/chronocrystal-opsx/tree/main/.pi/skills/kawa-clean
Command: npx skills add https://github.com/dentedgem9846-claw/chronocrystal-opsx --skill kawa-clean

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kill all running Kawa and simplex-chat processes and remove test artifacts.

Core Features & Use Cases

  • Terminate stale kawa and simplex-chat processes to restore clean state.
  • Remove listed temporary directories to prevent flaky starts after tests.
  • Provide a quick path to start Kawa reliably after cleanup.

Quick Start

Run npm run clean from the flux/kawa project to terminate processes and delete temp directories, then start Kawa with npm run start:kawa.

Frequently Asked Questions about kawa-clean

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

FAQPage Schema
How do I kill stale Kawa and simplex-chat processes left over after debugging?

To kill stale Kawa and simplex-chat processes, run the npm run clean script from the flux/kawa project directory. This terminates lingering processes and restores a clean state for debugging or smoke tests.

Why does Kawa fail to start with leftover temp directories after running tests?

Kawa may fail to start due to leftover temporary directories in /tmp causing conflicts. Running an npm cleanup script removes these test artifacts and prevents flaky starts.

Can I use npm scripts to manage process cleanup and restart Kawa in one workflow?

Yes, you can run npm run clean to terminate processes and remove temp directories, then immediately execute npm run start:kawa to reliably restart the application in a clean state.

What is the best way to purge test artifacts and reset the Kawa environment?

The best way to purge test artifacts and reset Kawa is running the npm clean script, which kills simplex-chat processes and deletes listed /tmp directories to ensure a stable startup environment.

What should I do when Kawa process cleanup doesn't fix startup failures?

If Kawa startup failures persist after process cleanup, verify that all simplex-chat processes are terminated and all specified /tmp test artifact directories are fully removed before attempting to restart.