Task runners beyond make: just, npm scripts and Invoke for project commands

What it is

A task runner gives a project one place for its commands (build, test, lint, db-reset) so that people, agents and CI invoke the same thing. make is the classic tool but carries build-system semantics (file targets, timestamps, tab-indented recipes) that project commands do not need. The just manual states that commands, called recipes, are stored in a file called justfile with syntax inspired by make, and describes just as a command runner, not a build system, so there is no file-freshness logic to fight; recipes take parameters, and just --list prints them with the comment immediately preceding each recipe. npm scripts live in package.json; the npm documentation describes life cycle scripts and pre and post hooks (pretest runs before test), and npm run adds locally installed executables to the PATH so tools need no global install. Invoke is Python: functions decorated with @task in a tasks.py receive a context object, get argument parsing and help generated for them, and run shell commands through the context.

Why it matters

The value is the contract, not the tool: any collaborator runs just --list or npm run and sees every supported command, and CI calls the same names. When a command changes, it changes in one file rather than in a README, a workflow file and several shell histories.

How to apply

• Pick the runner that matches the project's primary language so no extra toolchain is needed: npm scripts for Node projects, Invoke for Python, just where the repository spans languages or has no runtime of its own.
• Keep recipes short; anything beyond a few lines becomes a script under scripts/ that the recipe calls, so it can be linted and tested.
• Give every recipe a one-line description: just shows the comment preceding a recipe in just --list, and Invoke prints the first line of a task's docstring in invoke --list.
• Make recipes work from any directory and without prompts; set the shell explicitly and fail on error in shell-backed recipes.
• Mirror the names across repositories (setup, test, lint, fmt, run) so knowledge transfers.
• Let CI call the recipe, not a copy of its contents; see the related methodology on keeping CI and local checks identical.

Pitfalls

npm scripts are shell strings, so quoting and portability between shells vary, and pre and post hooks run implicitly, which surprises readers. just must be installed separately, one more step for the bootstrap script. Invoke's tasks.py is ordinary Python, so an import error in the environment it runs in also breaks the task list. None of the three tracks file freshness; use a build tool for incremental builds.