task-runner
Scannednpx machina-cli add skill aiskillstore/marketplace/task-runner --openclawTask Runner
Purpose
Execute project-specific commands using just, a modern command runner that's simpler than make and works cross-platform.
Tools
| Tool | Command | Use For |
|---|---|---|
| just | just | List available recipes |
| just | just test | Run specific recipe |
Usage Examples
Basic Usage
# List all available recipes
just
# Run a recipe
just test
just build
just lint
# Run recipe with arguments
just deploy production
# Run specific recipe from subdirectory
just --justfile backend/justfile test
Common justfile Recipes
# Example justfile
# Run tests
test:
pytest tests/
# Build project
build:
npm run build
# Lint code
lint:
ruff check .
eslint src/
# Start development server
dev:
npm run dev
# Clean build artifacts
clean:
rm -rf dist/ build/ *.egg-info/
# Deploy to environment
deploy env:
./scripts/deploy.sh {{env}}
Discovery
# Check if justfile exists
just --summary
# Show recipe details
just --show test
# List recipes with descriptions
just --list
When to Use
- First check:
justto see available project commands - Running tests:
just test - Building:
just build - Any project-specific task
- Cross-platform command running
Best Practice
Always check for a justfile when entering a new project:
just --list
This shows what commands are available without reading documentation.
Source
git clone https://github.com/aiskillstore/marketplace/blob/main/skills/0xdarkmatter/task-runner/SKILL.mdView on GitHub Overview
Task Runner uses the just CLI to execute project-specific commands. It can list available recipes, run common tasks like test, build, and lint, and execute project scripts. It relies on a justfile at the project root to drive actions.
How This Skill Works
The tool detects a justfile at the repository root and uses just to run defined recipes. You can list recipes with just --list, inspect details with just --show, or execute a recipe like just test or just build. You can also target a specific justfile in a subdirectory, for example just --justfile backend/justfile test.
When to Use It
- To see available recipes in the repo using just --list.
- To run tests quickly with just test.
- To build the project with just build.
- To lint the codebase with just lint.
- To run a deployment or environment-specific task, e.g. just deploy production or just --justfile backend/justfile test.
Quick Start
- Step 1: Install just: brew install just (macOS) or cargo install just (cross-platform).
- Step 2: From the project root, list available recipes with just or just --list.
- Step 3: Run a recipe, for example just test or just build.
Best Practices
- Always verify a justfile exists by listing recipes (just --list).
- Prefer using standard tasks (test, build, lint) before custom scripts.
- Use explicit justfile paths when working with multiple configurations (e.g., just --justfile backend/justfile test).
- Document new recipes within the justfile to improve discoverability.
- Run commands from the project root to ensure correct path resolution.
Example Use Cases
- List available recipes in the repo: just --list.
- Run the test suite: just test.
- Build the project for distribution: just build.
- Lint the codebase: just lint.
- Deploy to production: just deploy production.