validatelisted

# Validate Changes Skill ## Purpose Run linting, type checking, and unit tests to validate changes before pushing to GitHub. ## Usage ```bash /validate ``` (Must be run after `/test`) ## What This Skill Does 1. **Load Test Files**: Reads unit test files from `unit-tests.md` 2. **Run Linting**: Executes ESLint/Stylelint/TypeScript checks 3. **Run Type Checking**: Validates TypeScript types 4. **Run Unit Tests**: Executes all unit tests 5. **Validate Coverage**: Ensures coverage meets thresholds 6. **Output Results**: Saves validation results to `validation-results.md` ## Implementation Plan Context The unit tests should be located in the most recent directory under `workflow/jira-to-github/*/unit-tests.md`. You will need to find and read this file in Step 1. ## Instructions You are validating the code implementation through testing. Follow these steps: ### Step 1: Validate Prerequisites and Load Repo Context Verify that: 1. Code changes have been implemented 2. Unit tests have been created **CRITICAL — Load validation commands from repo context BEFORE running anything:** 1. Read `workflow/jira-to-github/*/target-repo.md` to get the repo path and profile path 2. Read the repo profile at the path specified (e.g., `context/repos/esperanto.md`) to get the `Context Files` pointers and `PR Template > Testing` checklist 3. Read the repo's own CLAUDE.md at `<repo-path>/CLAUDE.md` and look for a `Commands` section (or similar: "Validation Commands", "Testing", "Developme