Validate

---
name: validate
description: Use before commit, /merge-to-main, /workday-complete, or to validate repo state. Runs CI checks locally.
description-budget: 175
version: 1.0.0
---

# Local CI Validation

Run all CI checks locally to catch issues before they hit the remote pipeline.

## What It Does

Executes `.github/scripts/run-all-checks.py`, which uses convention-based discovery to find and run all `validate-*.py` and `check-*.py` scripts in `.github/scripts/`.

## How to Run

```bash
python .github/scripts/run-all-checks.py
```

Run this command using the Bash tool. Read the full output — every script's pass/fail status and any error details.

## When to Use

- Before committing significant changes
- Before `/merge-to-main` or `/workday-complete`
- After modifying CI scripts, plugin manifests, settings, or memory files
- When the user asks "does everything pass?" or "validate"

## Interpreting Results

- **All PASS**: Safe to proceed with commit/merge
- **Any FAIL**: Fix the failing check before proceeding. The output includes the script name and error details.
- **Script not found**: The repo may not have CI scripts set up. This is not an error in other repos — only applies where `.github/scripts/` exists.

## Integration

This skill complements `verification-before-completion`. That skill requires evidence before claims; this skill provides the evidence for repo-level validation claims.

## Common Mistakes

- **Forgetting to stage files before validating.** Unstaged changes won't be caught by some checks — ensure your working tree reflects intent before running.
- **Committing secrets or credentials.** Check for `.env` files, API keys, and private tokens before staging. CI may catch these, but prevention is better.
- **Skipping JSON and YAML validity checks.** Malformed frontmatter or settings JSON silently breaks plugin loading. Run the validator even for "small" config edits.
- **Leaving empty chunk or stub files.** Empty files in `docs/plans/` or `tasks/` directories can confuse downstream pipeline tools — delete or populate before committing.
- **Not reading the full output.** Skimming past FAIL lines or truncated error details means fixing the wrong thing. Read every script's result completely.