Build, Test, and Lint Configuration

After implementation, the skill can optionally run a build verification command to catch regressions introduced by the task’s changes. This is configured via aitasks/metadata/project_config.yaml and applies to all three implementation skills: /aitask-pick, /aitask-pickrem, and /aitask-pickweb.

Configuration

# Single command
verify_build: "cargo build"

# Multiple commands (run sequentially, stop on first failure)
verify_build:
  - "npm install"
  - "npm run build"
  - "npm test"

If verify_build is not set (or the file doesn’t exist), the step is skipped entirely.

How It Works

The project_config.yaml file is:

• Git-tracked — shared across the team (unlike userconfig.yaml which is per-user)
• Project-specific — not tied to execution profiles (the same build command applies regardless of which profile you use)
• Installed from seed — a template is copied during ait setup; edit it to match your project

Failure Handling

If the build fails, the agent analyzes whether the failure is caused by the task’s own changes:

• Task-related failure: The agent automatically goes back to fix the errors and re-runs the build. This repeats until the build passes.
• Pre-existing failure: The agent logs the build failure details in the plan file’s “Final Implementation Notes” and proceeds without attempting to fix unrelated issues.

Common Examples

Test and Lint Commands

In addition to build verification, project_config.yaml supports test_command and lint_command keys used by /aitask-qa for test execution and linting.

# Test command — used by /aitask-qa Step 4
test_command: "bash tests/test_*.sh"

# Lint command — used by /aitask-qa Step 4
lint_command: "shellcheck .aitask-scripts/aitask_*.sh"

# Multiple commands (run sequentially)
test_command:
  - "pytest tests/"
  - "npm test"

These are distinct from verify_build:

• verify_build runs automatically after implementation (Step 9 of /aitask-pick) to catch build regressions
• test_command and lint_command run on demand when /aitask-qa analyzes a task’s test coverage

Auto-detection Fallback

When test_command is not configured, /aitask-qa auto-detects test files matching common patterns:

Explicit configuration is recommended for reliable results — auto-detection may miss project-specific test layouts.

Common Examples