菜单
Kill all LexiQuest local dev processes (Azurite + Vite + Functions host + SWA CLI) and free their ports. Idempotent — safe to run when nothing is running. Use when the user wants a clean slate, when orphaned background processes are holding ports, or as a teardown after a debug session.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Fast pre-deploy sanity check that boots the real SWA + Functions stack locally against Azurite and exercises the critical-path routes end-to-end. Use before pushing to main (which auto-deploys) and whenever the API composition roots or static-web-app config change. Never touches real storage.
Start the full LexiQuest local development environment (Azurite + Vite + SWA CLI). ALWAYS kills any existing dev processes first, then starts clean — never tries to attach to a running stack. Use when the user wants to run the app locally, test a feature in the browser, or diagnose a runtime error that unit tests cannot catch.
Trigger and monitor a LexiQuest deploy to Azure Static Web Apps. Runs after `/local-smoke` passes. Push-to-main auto-deploys via GitHub Actions; this skill watches that run, tails logs, and probes the live URL until green. Never pushes force. Never rotates secrets.
Update the /docs folder at the end of a coding task. Use immediately after a `/tdd-cycle` completes (or any meaningful workspace change) to refresh the changelog, setup, getting-started, user guide, and PROGRESS as needed. Invoke proactively — documentation staleness is a bug.
Scan the LexiQuest workspace for secrets, credentials, and common security leaks. Runs as a mandatory step in every /tdd-cycle (after COVER, before UPDATE DOCS) and also on-demand when the user asks for a security check. Blocks the cycle if anything is found — never "note and continue".
Run the LexiQuest TDD cycle for a coding task. Use at the start of ANY code change (feature, bug fix, refactor) to write and get approval on a plan, then produce the RED test list, confirm failing tests, scaffold testable seams, implement to GREEN, refactor, and verify tier-appropriate coverage + requirement traceability. Invoke proactively — never write production code without running this first.
| name | dev-stop |
| description | Kill all LexiQuest local dev processes (Azurite + Vite + Functions host + SWA CLI) and free their ports. Idempotent — safe to run when nothing is running. Use when the user wants a clean slate, when orphaned background processes are holding ports, or as a teardown after a debug session. |
Kill every LexiQuest dev process and free every dev port. This is the
canonical teardown — /dev-start runs the same block as its first
step. If you change how things stop, change it here, not in dev-start.
The skill is idempotent: running it when nothing is running is a
no-op, not an error. It is also safe to run from any working directory
(no cd required).
pkill -9 -f "swa start" 2>/dev/null
pkill -9 -f "func start" 2>/dev/null
pkill -9 -f "vite" 2>/dev/null
pkill -9 -f "azurite" 2>/dev/null
# belt-and-braces: free the ports even if a stray child survived pkill
lsof -ti :4280,5173,7071,10000,10001,10002 2>/dev/null | xargs -r kill -9 2>/dev/null
sleep 1
pkill ... 2>/dev/null returns non-zero when nothing matched — that is
fine, it just means nothing of that kind was running. Do not treat it as
a failure.
lsof -i :4280,5173,7071,10000,10001,10002 | grep LISTEN
# expect: NO output
If anything is still listed:
# show what's holding each port
lsof -i :4280,5173,7071,10000,10001,10002 -sTCP:LISTEN
# kill the specific PID
kill -9 <PID>
A common stragglers list and what to do:
Process name in lsof | What it is | How to stop |
|---|---|---|
node on 5173 | Vite dev server | already covered by pkill -f vite |
node on 4280 | SWA emulator | pkill -9 -f "swa start" |
func on 7071 | Functions host | pkill -9 -f "func start" |
node on 10000-10002 | Azurite | pkill -9 -f azurite |
node started by npm run wrapping vite/swa | the wrapping npm survives pkill of the child sometimes | lsof -ti :<port> | xargs kill -9 |
Report one line:
/dev-stop OK — all ports free
or, if any port stayed busy:
/dev-stop PARTIAL — :7071 still held by PID 12345 (`func`)
…and follow up with the explicit kill -9 <PID>.
/tmp/azurite). The user may want
their seeded tables back when they next run /dev-start. Teardown of
data is a separate, more dangerous operation.ANTHROPIC_API_KEY or any other env var in the
user's shell. The skill manipulates processes only.node or func processes. The pkill -f
patterns here are scoped to the LexiQuest dev tooling. If a func
host on a non-LexiQuest port (e.g. 7072) is also running, leave it.