菜单
Use this skill when the user is surprised that a new `.nix` file was automatically discovered, or needs to understand why files under `modules/` are auto-imported as flake-parts modules. Applies when discussing module discovery, auto-import, or file placement conventions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
After `nix flake update`, sync `input_rev` and `input_hash` metadata in all flake-input skill files to match new `flake.lock`.
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
| name | import-tree |
| description | Use this skill when the user is surprised that a new `.nix` file was automatically discovered, or needs to understand why files under `modules/` are auto-imported as flake-parts modules. Applies when discussing module discovery, auto-import, or file placement conventions. |
| metadata | {"input_rev":"d321337efd0f23a9eb14a42adb7b2c29313ab274","input_hash":"sha256-Jjuz5CmSkur8KvLDoGa+vylEp+RkQtv4mt/qcMznpH0=","when_to_use":"import-tree, auto-import, file discovery, module loading"} |
grep -A4 '"import-tree"' flake.lock | grep narHash
Expected: sha256-Jjuz5CmSkur8KvLDoGa+vylEp+RkQtv4mt/qcMznpH0=
If different, update metadata.input_hash and metadata.input_rev.
.nix file anywhere under modules/ — it is automatically discovered and fed to mkFlake as a flake-parts module.modules/ must be a valid flake-parts module (a function accepting { inputs, self, ... }). Raw Nix expressions break the build.except list at flake.nix:111 (e.g., _nixvim-config.nix).except parameter takes absolute paths relative to the workspace root. Use ./modules/homeManagerModules/_nixvim-config.nix, not a bare filename..nix file with a stray syntax error anywhere under modules/ breaks the entire flake evaluation, not just the module you're working on.grep -c "import-tree" flake.nix && nix eval .#nixosConfigurations.epsilon.config.system.stateVersion --raw 2>/dev/null