Builds a CI workflow that runs only the subset of tests impacted by a PR's changes - combines a per-test → source-file dependency map (built from coverage profiles or, in build-graph projects, queried from the build system itself like Bazel `rdeps`) with the PR's `git diff --name-only`, then selects the union of (impacted by changed files + previously failing + newly added). Always pairs with a periodic full-suite run so a misconfigured map can't silently shrink coverage. Use when the regression suite is large enough that PR-time CI is the bottleneck and a full run is reserved for nightly / pre-release.
69
87%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Low
Low-risk findings.
2 low severity findings. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The skill’s runtime workflow ingests outsider-authored free text from the PR by running `git diff --name-only ... HEAD` and uses those changed filenames (provided with the PR) to select tests.
PR changed-file list via git diff --name-only
content-type · 4 sites
The plugin's workflow runs `git diff --name-only` to obtain PR-authored filenames, which are outsider-controlled free text used to select which tests to run, enabling indirect prompt injection or test-selection manipulation.
references/instrumentation-and-ci.md
63
CHANGED=$(git diff --name-only origin/${{ github.base_ref }}...HEAD)
38
CHANGED=$(git diff --name-only origin/main...HEAD | sed 's|^|//|')
SKILL.md
89
git diff --name-only origin/${{ github.base_ref }}...HEAD
112
git diff --diff-filter=A --name-only
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
The workflow uses the GitHub Action reference "actions/checkout@v5", which is fetched and executed at runtime by GitHub Actions (remote code execution), so this is a runtime external dependency that executes remote code.
actions/checkout@v5
dependency · 2 sites
The CI workflow uses `actions/checkout@v5`, a GitHub Action fetched and executed at runtime from the GitHub Actions marketplace, constituting an unverifiable external dependency.
references/instrumentation-and-ci.md
58
- uses: actions/checkout@v5
references/instrumentation-and-ci.md
74
- uses: actions/checkout@v5