Kill zombie dev servers and test processes. Use when ports are blocked, processes are hanging, or test runners won't start.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
Kill zombie processes (dev servers, Playwright browsers, test runners) for the current project only. Safe to use in multi-project environments.
Run the cleanup script with --dry-run first to preview what will be killed:
./.safeword/scripts/cleanup-zombies.sh --dry-run
If the output looks correct, run without --dry-run:
./.safeword/scripts/cleanup-zombies.sh
packages/*/, apps/*/ for monorepos)If auto-detection fails or you need a specific port:
# Explicit port
./.safeword/scripts/cleanup-zombies.sh 5173
# Port + additional pattern
./.safeword/scripts/cleanup-zombies.sh 5173 "electron"
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Run comprehensive code audit for architecture, dead code, and test quality. Use when reviewing overall codebase health, checking for architectural violations, or before marking a feature complete.
The English summary is being prepared. Showing the original description.
Behavior-first feature development — use when building new capabilities, continuing feature work, or when work introduces new state or multiple user flows. Discovers desired behavior through examples and scenarios before implementation. Do NOT use for bug fixes, typos, or small isolated changes.
The English summary is being prepared. Showing the original description.
Use when the user wants to explore options, weigh approaches, or think through uncertainty before committing to a direction. Collaborative brainstorming and rubber ducking — divergence-first thinking partner.
The English summary is being prepared. Showing the original description.
Root cause debugging before fixes. Use when investigating bugs, diagnosing test failures, troubleshooting unexpected behavior, or when previous fix attempts failed. Enforces investigate-first discipline.
The English summary is being prepared. Showing the original description.
Extract tacit knowledge through non-obvious microquestions — things only the user knows that can't be found in code, docs, or research. Use when you're about to guess at intent, context, or constraints during SAFEWORD's understanding flow. Also use when user says 'ask me', 'what do you need to know', or when another skill (bdd, brainstorm, debug) needs user context before proceeding. Do NOT use for questions answerable by reading the codebase or searching the web.
The English summary is being prepared. Showing the original description.
Explore and debate options with fresh documentation and research before committing. Use when facing a real decision with multiple plausible approaches — library/framework choice, architecture call, API or schema design, algorithm selection, or any communication / strategy call where being wrong has cost. Enumerates relevant research domains, looks up current docs and evidence-based methods, weighs options on correctness and elegance, resists bloat. Do NOT use for divergent ideation (brainstorm), extracting user intent (elicit), or reviewing already-written code (quality-review).
The English summary is being prepared. Showing the original description.