dependabot

Configure and manage GitHub Dependabot dependency update workflows.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/lettucebo/Skills --skill dependabot-lettucebo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dependabot
Source: https://github.com/lettucebo/Skills/tree/main/skills/github/dependabot
Command: npx skills add https://github.com/lettucebo/Skills --skill dependabot-lettucebo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Keeping dependencies current and secure across repositories requires writing and tuning .github/dependabot.yml files, which involves many ecosystem values, grouping rules, and scheduling options that are easy to misconfigure. ## Core Features & Use Cases - Ecosystem Detection and Configuration: Identify all package ecosystems in a repository (npm, pip, Docker, Terraform, and more) and generate correct dependabot.yml entries for each. - PR Noise Reduction: Apply dependency grouping, cross-directory monorepo grouping, multi-ecosystem groups, cooldown periods, and scheduling to batch updates into fewer pull requests. - Security Update Management: Configure grouped security updates, auto-triage rules, and pre-commit dependency vulnerability scanning via the GitHub MCP Server. - Use Case: A monorepo with npm workspaces, Docker images, and GitHub Actions can use this Skill to produce a single dependabot.yml that groups dev dependencies weekly, batches shared dependencies across directories, and limits security patches to grouped PRs. ## Quick Start Ask the agent to scan this repository and generate an optimized dependabot.yml with grouped updates for every detected ecosystem.

Frequently Asked Questions about dependabot

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

FAQPage Schema
How do I configure Dependabot for a monorepo?▼

Use the `directories` key with glob patterns like `/apps/*` and `/packages/*` to cover all workspace packages in one entry. Add `group-by: dependency-name` in a group to create a single PR when the same dependency updates across multiple directories.

How do I reduce Dependabot pull request noise?▼

Group related dependencies with the `groups` key using patterns, dependency-type, or update-types filters so they ship in one PR. You can also switch to monthly intervals, set cooldown periods, or use multi-ecosystem groups to batch updates further.

Does Dependabot support pnpm and yarn?▼

Yes. Use `package-ecosystem: "npm"` and Dependabot automatically detects `pnpm-lock.yaml` and `yarn.lock`. There is no separate pnpm or yarn ecosystem value.

Can I have multiple dependabot.yml files in one repository?▼

No. GitHub supports exactly one file at `.github/dependabot.yml` on the default branch. Use multiple `updates` entries within that file to cover different ecosystems and directories.

How do I disable version updates but keep security updates?▼

Set `open-pull-requests-limit: 0` on the ecosystem entry, which disables version update PRs while security updates continue. You can also group security patches with `applies-to: security-updates` in a group.

Why did the @dependabot merge command stop working?▼

GitHub deprecated the merge, close, and reopen PR comment commands in January 2026. Use GitHub's native auto-merge feature, the web UI, or `gh pr merge` from the CLI instead.