Index of every page on this site: llms.txt
All skills
Run it yourself

Audits a repository's GitHub Actions workflows for CI optimization opportunities — missing caches, redundant setup, sleep-based readiness, long test jobs without sharding, full-history checkout, dead env vars, build-cache misconfig, and ~60 more patterns across caching, redundancy, parallelization, conditional execution, trigger scope, and hidden failures. Use when: (1) analyzing a repo's CI for optimization opportunities, (2) producing a prioritized report with measured wall-clock and runner-minute savings, (3) re-auditing after upstream CI changes. Do not trigger for: general CI setup help, writing new workflows from scratch, non-GitHub-Actions CI systems, or security/posture audits — use `ci-secure` for those.

Use this Skill: https://skilld.dev/gh/starslingdev/skills/ci-speedup

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencespatternsopt38-non-content-trigger-event-types-pr-edited-etc.md

≈833 tokens on demand. Your agent reads this file only when SKILL.md points to it.

OPT38 — Non-Content Trigger Event Types (PR edited, etc.)

Anti-pattern: A workflow's on.pull_request.types includes events that don't change the code under test, causing the full workflow to re-run on metadata-only changes. The most common offenders:

  • edited — fires when the PR title, description, or base branch is edited. Title typo fix → full CI re-run.
  • labeled / unlabeled — fires when any label is added/removed. Most workflows don't gate on labels and re-run for nothing.
  • assigned / unassigned, review_requested, review_request_removed — same story.
  • ready_for_review — legitimate (draft → ready transition); KEEP this one if you want CI to start when a draft becomes ready.

The default pull_request types are [opened, synchronize, reopened] — these are the content-change events. Anything beyond that needs justification.

Detection heuristic:

# Find workflows that override pull_request.types
grep -rA3 'pull_request:' .github/workflows/ | grep -E 'types:.*edited|types:.*labeled'

For each hit:

  1. Confirm the types: array includes one of the non-content events.
  2. Cross-reference the workflow body for any if: github.event.action == 'labeled' (or similar) — if present, the trigger is intentional.
  3. Inspect what the workflow reads before calling a re-run a no-op. List every uses: target and every script the jobs run, and look for a dependency on the PR title, description, labels, base branch, or other PR metadata, with or without an if: guard. A PR-title validator such as amannn/action-semantic-pull-request, a label-driven check, or a description linter reads that metadata internally, so its job needs the matching event type to run again. Keep every event type needed to rerun those checks.
  4. Only when that inspection finds no metadata dependency, the metadata events trigger a full no-op re-run.
  5. Cost = full workflow P50 × estimated frequency of metadata edits (typically 5-20% of PR activity).

Fix: Restrict types: to content-change events:

on:
  pull_request:
    types: [opened, synchronize, reopened, ready_for_review]

Or simply omit types: to use the default (which already excludes edited).

Real-world example (blen-starter-kit deep-scan): ci.yml and several other workflows would re-run on PR title/body edits because of an inherited types: array including edited. Fix is a one-line YAML change.

Risk: LOW once step 3 finds no metadata dependency; not LOW before it. An if: guard is not the only sign a workflow needs the event. Two cases need it with no guard at all:

  • An action or script that reads PR metadata internally (a PR-title validator, a label-driven check, a description linter). Dropping edited or labeled leaves a corrected title failing, or an invalid one passing, on a stale result.
  • edited also fires when the pull request's base branch changes. Dropping it means CI does not run again after a retarget, so a PR can show green against its old base.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alert2d3 checks · Risk SAFE
  • Gen Agent Trust Hub2d

    The skill is a robust CI optimization tool that audits GitHub Actions workflows. It identifies performance bottlenecks using deterministic logic and provides analysis of job logs. While it processes untrusted log data, it includes strong defensive instructions to mitigate indirect prompt injection. A minor best-practice issue regarding unsafe YAML loading was identified in a utility script.

  • Socket2d

    No alerts

  • Snyk2d

    Risk: CRITICAL · 2 issues

Signed by skilld at 9a84115. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 16 hours ago.

Activeupdated yesterday

README badge

README badge for starslingdev/skills/ci-speedup