check-ci

# Check GitHub Actions CI Results Inspect the latest (or specified) GitHub Actions run for the current repository, report job statuses, and **automatically fix any failures found**. ## Step 1: Identify the run If $ARGUMENTS contains a run ID, use that. Otherwise, find the latest run for the current branch: ``` gh run list --branch $(git branch --show-current) --limit 1 ``` ## Step 2: Show job-level summary ``` gh run view <run-id> --json jobs --jq '.jobs[] | {name, status, conclusion}' ``` Report each job as PASS / FAIL / IN PROGRESS. ## Step 3: Get failed logs If any job failed: ``` gh run view <run-id> --log-failed ``` Save the output to a temp file and search it for: - Lines matching `--- FAIL` (test failures) - Lines matching `##[error]` (lint / build errors) - Lines matching `FAIL\t` (package-level failures) ## Step 4: Report For each failure found, report: 1. **Job name** (e.g., test-windows, test-linux) 2. **Failure type** (test failure, lint error, build error) 3. **Details** — the test name, error message, or lint diagnostic 4. If the run is still in progress, say so and suggest checking back later. Keep the report concise. Group failures by job. If all jobs passed, just say "CI passed" and stop here. ## Step 5: Fix failures If there are failures, fix them: 1. **Diagnose** — Read the failing source files and tests identified in Step 4. Understand the root cause of each failure (broken test logic, lint violation, build error, type mismatch, etc....