commit-preflight

To run GitHub Actions workflow checks locally before pushing, the Skill reads your `.github/workflows/*.yml` files, matches branch and path filters against your staged files, and executes local equivalents of the workflow steps to block avoidable CI failures.

Yes, you can automatically fix CI linting errors on staged files before a push. The Skill performs scope-safe repairs, auto-fixing only failures that can be resolved within your candidate file set while reporting exact blockers for out-of-scope issues.

Local CI preflight handles missing dependencies by probing your environment for required tools and prompting you for approval before installing only the specific dependencies needed to execute the matching workflow steps deterministically.

Running a preflight check differs from simple workflow linting because it builds an ordered execution plan from matching `run` and `uses` steps, probes dependencies, captures exit statuses, and returns an allow, block, or residual-risk decision with a concise audit summary.

Yes, commit preflight works directly with path filters and branch triggers. It inspects active GitHub Actions workflow gates by reading the YAML files and selecting only workflows whose `branches`, `paths`, and other filters match the candidate commit or unpushed branch.