菜单
Use when the user says "start the dev server", "restart the server", "check the server logs", "what's the server error", or any dev-server lifecycle phrasing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user says "/deep-review", "deep review", "thorough review", or wants the deepest possible code review before pushing a branch.
Use when the user says "/harness-update", "update the harness", "upgrade agent-harness", "pull the latest harness", or after seeing an UPGRADE_AVAILABLE notice. Pulls latest harness files into this project, preserves project-specific configuration and local-only skills, and walks the user through any conflicts.
Use when the user wants to audit or understand the agent harness itself — its hooks, skills, agents, or commands — or asks "what's in this harness", "how does this harness work", or "harness overview".
Use when the user has a one-off task that slots into the current sprint and needs a quick written plan — lighter than /plan-sprint. Reads existing plans for context, uses plan mode, writes a focused plan file.
Use when the user says "/build", hands off a sprint-plan document path, or asks to execute a written plan end-to-end. Branches, implements, tests, verifies in browser, commits incrementally, and prepares the PR. Auto-fires /lg-* skills when plan steps involve LangGraph/LangChain agent work.
Use when the user says "review migrations", "db review", "check schema changes", "safe to migrate?", or before deploying schema changes to production.
| name | dev-server |
| description | Use when the user says "start the dev server", "restart the server", "check the server logs", "what's the server error", or any dev-server lifecycle phrasing. |
| user-invocable | true |
| tier | util |
Start, stop, and monitor the local development server. Use when the user says "start the dev server", "restart the server", "check the server logs", "what's the server error", or similar.
Read .claude/hooks/config.sh for:
HARNESS_DEV_CMD — command to start the dev server (e.g., pnpm dev)HARNESS_DEV_PORT — fallback port when not in a Conductor workspace (default: 3000)HARNESS_DEV_PROCESS — process name pattern for pkillHARNESS_APP_NAME — used for log file namingPort resolution: When determining which port the dev server is actually bound to, prefer ${CONDUCTOR_PORT:-$HARNESS_DEV_PORT}. Inside a Conductor workspace, conductor.json's run script starts the server on $CONDUCTOR_PORT. Outside Conductor, it's $HARNESS_DEV_PORT.
Create the logs directory:
mkdir -p /tmp/${HARNESS_APP_NAME// /-}-logs
Kill any existing dev server to avoid port conflicts:
pkill -f "$HARNESS_DEV_PROCESS" 2>/dev/null || true
Wait 2 seconds for ports to release.
Start the dev server in the background using the Bash tool with run_in_background: true:
cd $(git rev-parse --show-toplevel) && $HARNESS_DEV_CMD 2>&1 | tee /tmp/${HARNESS_APP_NAME// /-}-logs/dev.log
Tell the user:
tail -f /tmp/<app-name>-logs/dev.logWhen asked about server errors or logs, use TaskOutput to read the background task output. Also check:
tail -100 /tmp/<app-name>-logs/dev.log
pkill -f "$HARNESS_DEV_PROCESS" 2>/dev/null || true