github-actions-dependabot-review

Reviews Dependabot PRs for GitHub Actions updates with security-focused upstream diff analysis.

78|27|Updated May 4, 2024
One-click install
npx skills add https://github.com/fedixyz/fedi --skill github-actions-dependabot-review-fedixyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-actions-dependabot-review
Source: https://github.com/fedixyz/fedi/tree/main/.agents/skills/github-actions-dependabot-review
Command: npx skills add https://github.com/fedixyz/fedi --skill github-actions-dependabot-review-fedixyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Dependabot PRs that bump GitHub Actions versions can silently introduce malicious or risky upstream changes, and manually auditing each action's upstream diff is tedious and easy to skip. ## Core Features & Use Cases - Duplicate Review Detection: Checks whether a human already reviewed the PR before doing redundant work. - Upstream Diff Audit: Compares old and new revisions of the action repository using Dependabot-provided hashes, checking for secret exfiltration, shell injection, new network calls, and suspicious minified artifacts. - Dependency and Lockfile Review: Inspects changed manifests like package-lock.json or Cargo.lock, verifying registry metadata and release age when diffs are too large. - Use Case: A maintainer receives a Dependabot PR titled "bump actions/checkout from v4 to v5" and asks the agent to review it; the agent audits the upstream diff, compares it against the changelog, and posts an OK/not-OK-to-merge comment. ## Quick Start Review the open Dependabot PRs that update GitHub Actions workflows and post a security assessment comment on each one.

Frequently Asked Questions about github-actions-dependabot-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review Dependabot PRs for GitHub Actions updates?

Identify PRs with github_actions in the branch name or a bump-style title, then compare the old and new upstream action revisions using the hashes Dependabot provides. Verify the diff matches the changelog and check for security risks before approving.

What security risks should I check in a GitHub Actions version bump?

Check for secret or token exfiltration, eval or dynamic code execution, shell injection, new network calls or downloads, unexpected dependency changes, token permission handling, workflow-command injection, and suspicious minified artifacts.

How do I handle Dependabot PRs that change lockfiles like package-lock.json?

Review each dependency update in the lockfile the same way as the main action diff. If the diff is too large, check registry metadata and confirm the new version is at least a week old, raising anything unclear as a concern.

What happens if a Dependabot PR was already reviewed by a human?

The review is skipped for that PR. The workflow checks for an existing non-bot human review first and simply reports that the PR was already reviewed instead of duplicating the work.

When should a Dependabot GitHub Actions update not be merged?

Do not merge when the upstream diff does not match the changelog, contains suspicious code such as obfuscated artifacts or unexpected network calls, or when dependency updates cannot be verified as safe.