What problem does it solve? A paths: filter on a GitHub Actions workflow decides whether the workflow runs at all. When the filter omits the workflow file itself, the Dockerfile, the Makefile, or the lockfile, a change to how the gate runs can skip the gate entirely — producing a green required check with zero jobs executed. This Skill audits and authors paths-gated workflows so every input that can change the result is listed. ## Core Features & Use Cases - Paths-filter authoring: Provides a core YAML pattern and per-workflow checklist covering the workflow file itself, threshold configs, report scripts, Dockerfile, .dockerignore, compose files, Makefile, test trees, bundler config, lockfile, and package manifest. - Silent-skip diagnosis: Detects required checks that report success with zero jobs executed, stale path entries pointing at renamed scripts, and filters that omit the workflow's own build inputs. - Repository-shape guidance: Applies the pattern across React SPA, Next.js, and component-library shapes, with the matching verification target (make lint-actionlint or make lint-workflows). - Use Case: After renaming a bundle-size report script, a pull request shows the bundle-size check green but no jobs ran. Use this Skill to find the stale path entry, add the workflow file and toolchain inputs to the filter, and re-verify with actionlint. ## Quick Start Audit the paths filters in my GitHub Actions workflows and add any missing inputs such as the workflow file itself, Dockerfile, Makefile, and lockfile.
