home / skills / ehtbanton / claudeskillsrepo / dependabot-config-generator
This skill generates a complete Dependabot configuration for GitHub projects, enabling automated dependency updates across npm, actions, and other supported
npx playbooks add skill ehtbanton/claudeskillsrepo --skill dependabot-config-generatorReview the files below or copy the command above to add this skill to your agents.
---
name: dependabot-config-generator
description: Generate Dependabot configuration for GitHub automated dependency updates. Triggers on "create dependabot config", "generate dependabot configuration", "dependabot setup", "github dependency updates".
---
# Dependabot Config Generator
Generate GitHub Dependabot configuration for automated dependency updates.
## Output Requirements
**File Output:** `.github/dependabot.yml`
**Format:** Valid Dependabot YAML configuration
**Standards:** GitHub Dependabot v2
## When Invoked
Immediately generate a complete Dependabot configuration for the project.
## Example Invocations
**Prompt:** "Create dependabot config for npm and GitHub Actions"
**Output:** Complete `.github/dependabot.yml` with npm and actions updates.
This skill generates a ready-to-use GitHub Dependabot configuration file (.github/dependabot.yml) for automated dependency updates. It targets Dependabot v2 YAML format and produces configuration tailored to the project's package ecosystems and update cadence. The output is a complete, valid YAML file ready to commit to the repository.
When triggered, the skill inspects the prompt and project context to determine relevant ecosystems (for example npm, GitHub Actions, Maven, or Python). It builds a Dependabot v2 YAML that defines update schedules, package-ecosystem entries, directory paths, and optional settings like open-pull-request limits, ignored updates, and security-only mode. The skill returns the full file content for immediate use.
Which file does this skill produce?
It generates the .github/dependabot.yml file formatted for Dependabot v2.
Can it handle monorepos and multiple ecosystems?
Yes — the skill can include multiple package-ecosystem entries and separate directories per entry.