Kill zombie dev servers and test processes. Use when ports are blocked, processes are hanging, or test runners won't start.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
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"
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.