Use Task Runners for Common Coding Tasks

Developers juggling multiple repositories know the pain of remembering each project's specific commands: is it npm run ci or pnpm install? ./gradlew build or mvn compile? Ham Vocke's updated guide from 2019 (refreshed after a reader request) solves this by introducing lightweight task runners — simple wrappers that let you run common tasks with consistent, short commands like run build or make test.
Option 1: A Bash Script
Create a file named run (or similar) at the root of your repo, make it executable (chmod +x run), and add functions for each task. Here's a Node.js example from the article:
#!/usr/bin/env bash
set -e
function install { npm run ci }
function build { npm run build }
function test {
npm run test:unit
npx run playwright
}
function format { npm run prettier --write }
if [[ $# -lt 1 ]]; then usage; exit 1; fi
TARGET=$1
case $TARGET in
"install") install ;;
"build") build ;;
"test") test ;;
"format") format ;;
*) echo "Unknown command"; usage; exit 1 ;;
esac
This script hides clunky arguments (like --write for prettier) and lets you chain multiple steps (e.g., unit tests plus Playwright). For more complex logic, you can extract functions into a bin/ directory.
Option 2: Make
Make is a 1970s build tool that's nearly universal. Using a Makefile with phony targets gives you the same convenience without extra scripting:
.PHONY: install build test format
install:
npm run ci
build:
npm run build
test:
npm run test:unit
npx run playwright
format:
npm run prettier --write
Just run make test or make format. Remember: make requires actual tabs for indentation.
Why Use a Task Runner?
Standardizing these commands means you can rely on muscle memory across projects, regardless of the underlying stack. It's a small overhead that pays off daily if you switch contexts often. As Vocke notes, these tools range from bash and make to modern options like mise and just, but the principle stays the same: one command to build, one to test, one to format.
📖 Read the full source: HN LLM Tools
👀 See Also

Recover deleted Claude Desktop conversations from Chromium cache
Immediately quit Claude Desktop, find the Chromium blockfile cache at %APPDATA%\Claude\Cache\Cache_Data (Windows), then use Python packages ccl_chromium_reader and standard compression libs to extract HTTP response bodies containing your chat UUID.

Research Shows Effective AI Prompting Is Cooperative Communication, Not Engineering
Peer-reviewed research indicates that effective prompting with AI models follows the same cooperative communication principles humans use, with Lakera's analysis showing most prompt failures stem from ambiguity rather than model limitations.

Practical fixes for OpenClaw reliability issues
A developer shares eight specific techniques that improved their OpenClaw setup, including a 3-tier memory system with daily logs and a knowledge graph, activation score management, and file-based rule enforcement.

Claude Certified Agent Foundations Exam Guide Discrepancies Identified
A recent CCA-F exam taker reports significant discrepancies between the official exam guide, practice exam, and actual test content. The real exam may include up to 13 scenarios while the guide only lists 6, and the practice exam covers just 4 of them.