taskrunner

name	taskrunner
description	Instructions for running project tasks. Use this when you need to run a project-specific command or workflow.

Taskrunner Skill

Instructions for running project tasks. All commands use Task as the task runner (see Taskfile.yaml).

Essential Commands

# Install dependencies (frozen lockfile, runs once per session)
task install

# Start development server with hot reload (cleans cache first)
task dev

# Create new blog post or page interactively
task new

# Generate GraphQL TypeScript types (skipped if src/gatsby-types.d.ts exists)
task typegen

# Lint codebase (tsc --noEmit + biome check)
task lint

# Format and lint codebase (biome check --write + terraform format)
task format

# Run full test suite (lint → unit → component → build → e2e)
task test

# Build for production
task build

# Serve production build locally on port 8000
task serve

# Clear build cache and delete src/gatsby-types.d.ts
task clean

Running Specific Tests

task test:unit always collects coverage (--coverage is baked into the task) and enforces the 100% threshold from vitest.config.ts. Filtering to a single file (as below) scopes the coverage report — and the threshold check — to just the files that test loads, so it stays accurate for one-file runs and won't fail because of unrelated gaps elsewhere in the codebase; it will still fail if the filtered file itself isn't fully covered.

# Run specific unit test file
task test:unit -- src/__tests__/unit/helpers.test.ts

# Run specific component test file
task test:component -- src/__tests__/components/article.test.tsx

# Run unit tests in watch mode
task test:unit:watch

# Run component tests in watch mode
task test:component:watch

# Run specific e2e test
task test:e2e -- src/__tests__/feature/index.test.ts

# Run e2e tests with UI mode
task test:e2e -- --ui

Common Workflows

After editing source code

task lint          # Verify no type errors or lint violations
task test:unit     # Run unit tests

After editing components

task lint              # Verify no type errors or lint violations
task test:component    # Run component tests in real browsers

Before opening a pull request

task test    # Full suite: lint → unit → component → build → e2e

After editing Markdown content

task build   # Verify the site builds successfully with the new content

Infrastructure & Deployment Tasks

The Terraform modules are exposed as root-level namespaces — no cd needed (see the terraform skill for details):

# Core infrastructure (runs in infra/cloudflare/)
task terraform:validate
task terraform:plan
task terraform:deploy

# Site deployment (runs in infra/site; needs `task build` first)
task site:validate
task site:plan WORKSPACE=pr-123
task site:deploy WORKSPACE=pr-123
task site:destroy WORKSPACE=pr-123

Gotcha: only pass -- <extra args> to tasks that run a single command. Multi-command tasks (e.g. site:destroy, site:plan) append {{.CLI_ARGS}} to every command they run, so extra flags break intermediate steps like terraform workspace select.

After editing infrastructure

task terraform:validate && task terraform:plan    # Validate and preview changes
task site:validate                                # When infra/site was touched