القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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 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.
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-authoring |
| description | 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. |
| auto_trigger | {"keywords":["write a script","add a task","scripts vs tasks","enterShell","exit code contract","authoring module","manager module","devenv task dependency"]} |
Pick the right surface:
scripts — a plain command on PATH. No ordering, no deps. Most CLIs.tasks — has dependencies/ordering (after/before) and runs in a defined sequence. Use
when one step must precede another.processes — long-running/supervised; started by devenv up. See devenv-processes.Two rules that bite agents:
Guard enterShell greetings so captured output isn't polluted:
enterShell = ''if [ -t 1 ]; then echo "…"; fi'';
Honor the exit contract: 0 ok · 1 decision/finding · 2 infra/config · 3 usage. A
tool's exit code is its API; don't collapse everything to 0/1.
Grep-able surface detail: scripts-tasks-processes.md. Building a *man-style module (options,
gated config, putting a CLI on PATH): the authoring-a-manager-module.md article.
For when in the lifecycle to author vs. verify, see the repoman skill.