dependabot-pr-automation

Reviews, risk-assesses, approves, and merges open Dependabot pull requests on GitHub.

583|54|Updated Mar 6, 2023
One-click install
npx skills add https://github.com/chainloop-dev/chainloop --skill dependabot-pr-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependabot-pr-automation
Source: https://github.com/chainloop-dev/chainloop/tree/main/.claude/skills/dependabot-pr-automation
Command: npx skills add https://github.com/chainloop-dev/chainloop --skill dependabot-pr-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually triaging a backlog of Dependabot pull requests is repetitive and error-prone: each PR requires checking the version bump type, CI status, and changed files before deciding whether it is safe to merge. This Skill automates that triage for the chainloop repository, applying a consistent risk matrix so low-risk dependency updates get merged quickly while risky ones are flagged.

Core Features & Use Cases

  • Automated PR triage: Lists open Dependabot PRs via the GitHub API and classifies each by version bump type (patch, minor, major).
  • Risk-based decisions: Combines CI check status, changed-file inspection, and dependency scope into a risk matrix that determines whether to approve, merge, or flag a PR.
  • Safe merging: Approves eligible PRs and merges them with squash, respecting branch protection rules and never force-merging.
  • Use Case: Ask the assistant to process the Dependabot queue before a release; patch and minor bumps with green CI are approved and squash-merged, while major bumps and failing PRs are reported for human review.

Quick Start

Review and merge all safe open Dependabot pull requests in the chainloop-dev/chainloop repository.

Frequently Asked Questions about dependabot-pr-automation

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

FAQPage Schema
How do I automatically merge Dependabot pull requests on GitHub?

List open PRs authored by dependabot[bot], verify all CI checks pass, confirm only dependency manifest files changed, then approve with a pull request review and merge using the squash method. This Skill performs that sequence via GitHub MCP tools.

How to assess risk of a Dependabot version bump?

Parse the old and new versions from the PR title to classify the bump as patch, minor, or major. Patch bumps with passing CI are low risk, minor bumps are medium risk, and major bumps or failing CI are high risk and should not be auto-approved.

Which Dependabot PRs are safe to auto-merge?

Patch bumps with passing CI that only modify dependency manifests like go.mod, go.sum, package.json, or lockfiles are safe to auto-merge. GitHub Actions patch and minor bumps with green CI are also treated as low risk.

Does this work with branch protection rules enabled?

Yes, the workflow respects branch protection rules and never force-merges. If a merge fails due to protection requirements or conflicts, the failure is noted and processing continues with the next PR.

What happens to major version bump PRs?

Major version bumps are always classified as high risk and are not approved or merged automatically. They are flagged in the final summary report so a maintainer can review them manually.