القائمة
Use when starting a server or any long-running / heavy task. Use processes + devenv up; don't block the shell; poll logs instead of piping out of view.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when writing a scripts/tasks/processes entry or a manager module. Covers which surface to use, guarding enterShell echoes, and the 0/1/2/3 exit contract.
Use when editing devenv.yaml or adding an input/import. Covers flake:false for modules, nixpkgs-python for version pins, and transitive inputs.
Use when you edited a modules/ file, devenv.nix, or env.* and nothing changed. Resolves the lock + eval-cache staleness loop.
Use on ModuleNotFoundError or import failures inside the devenv shell, or after a fresh venv. The venv exists but deps may not be installed.
Use when about to run pytest, python, uv, ruff, or any build/tooling command in this repo. Enforces running through the devenv shell.
Use on "command not found", the shell won't enter, or eval errors. A symptom→cause→fix decision tree for devenv repos.
| name | devenv-processes |
| description | Use when starting a server or any long-running / heavy task. Use processes + devenv up; don't block the shell; poll logs instead of piping out of view. |
| auto_trigger | {"keywords":["start a server","long running","background process","devenv up","daemon","watch","dev server","heavy build","poll logs"]} |
Don't block the shell on a server or a heavy build, and don't pipe output to a file you then can't see.
processes entry and run devenv up (optionally
devenv up <name>). It supervises them; it does not tie up your shell.scripts/tasks entry blocks until it exits; that's correct for short work, wrong for a
server.Grep-able surface comparison: scripts-tasks-processes.md. Worked example (processes, devenv up,
polling, not blocking): the background-and-long-running-work.md article.
For when in the lifecycle to start processes, see the repoman skill.