菜单
Use when running Python tools from the repo root with uv - prefer `uv run --project python` over `uv run --directory python`. The former keeps cwd unchanged; the latter breaks relative test paths.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Prepare for a /clear: bring all documentation up to date with this session's changes, persist recovery context (memory + handoff), and emit a copy-paste resume prompt so the next session begins the next task with zero context loss. Invoke explicitly as /clear-prep [next-task].
Use when adding or modifying a devcontainer feature in devcontainer.json - fetch its devcontainer-feature.json schema first and verify every option key exists, because features silently drop unknown options.
Use when creating branches, commits, pushes, or PRs with plain git. Branch BEFORE committing — never commit directly onto the default branch. Avoids virtual-branch composition bugs where commits silently depend on other applied branches.
Write a CROSS-SURFACE session handoff to a tracked path and push it, so a session on another surface (web, desktop, or CLI) can continue with zero context loss. Use when ending a session whose work must be picked up on a DIFFERENT machine/surface. For same-machine /clear continuity use /clear-prep instead. Invoke as /handoff [next-task].
Use when running parallel-scientist research - ALWAYS follow with an opus verification stage that re-probes load-bearing claims and surfaces gaps. Skipping the verifier almost shipped a wrong recommendation in session 2026-04-07e.
Use when sharing a single `~/.ssh/config` across macOS + Linux - apply OpenSSH `IgnoreUnknown` to tolerate macOS-only directives (`UseKeychain`, `AddKeysToAgent`) on Linux where they would otherwise be fatal.
| name | uv-project-vs-directory-expertise |
| description | Use when running Python tools from the repo root with uv - prefer `uv run --project python` over `uv run --directory python`. The former keeps cwd unchanged; the latter breaks relative test paths. |
uv run --directory <dir> changes the working directory to <dir> before running the command. uv run --project <dir> tells uv where to find pyproject.toml for dependency resolution WITHOUT changing cwd. When tests live outside the Python package directory (e.g., tests/ at repo root, package at python/), --directory breaks relative paths while --project preserves them.
Issue #43: the hk pre-push hook ran uv run --directory python pytest tests/ -x -q. With --directory, cwd changed to python/ and tests/ resolved to python/tests/ (nonexistent). This broke the pre-push hook silently — it appeared to be an hk bug but was a uv flag choice issue. Debugging was further complicated by hk's pkl config cache at ~/Library/Caches/hk/configs/ which showed stale commands.
ModuleNotFoundError for project deps when running pytest via uvuv run --directory python pytest "$PWD/tests" (absolute) but fail with relative paths--project when the command needs repo-root-relative paths (pytest, scripts)--directory only when the command itself should run from the package directoryrm -rf ~/Library/Caches/hk/configs/HK_LOG=debug hk run <hook> to see actual executed commands