dependabot-auto-merge
Skill2 starsChanged 8 months agoMITView on GitHub
Configure Dependabot auto-merge for a GitHub repository. Sets up automatic merging of Dependabot pull requests for patch and minor version updates, with optional CI check enforcement. Use this skill whenever the user wants to automate Dependabot PR merging, set up Dependabot workflows, configure branch protection for Dependabot, or enable auto-merge for dependency updates.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- azure-paas-supportSkill
- azure-resource-abbreviationsSkill
- backlog-apiSkill
- csharp-file-based-appsSkill
- devblog-updatesSkill
- github-changelogSkill
- github-entra-federated-credentialsSkill
- git-worktreeSkill
- hatena-blog-publisherSkill
- marp-cssSkill
- marp-deckSkill
- summarized-postSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 24
Write access to the repository
- Distinctive: line 36
If CI checks are not specified, the ruleset will only enforce deletion and force-push protection.
- Distinctive: line 49
After running this skill:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dependabot Auto-Merge Configuration
This skill automates the setup of Dependabot auto-merge for a GitHub repository. It configures:
- Auto-merge enablement - Allows PRs to be automatically merged when all checks pass
- Squash merge - Enables squash merge strategy for cleaner commit history
- Branch ruleset - Creates a ruleset for the default branch with:
- Deletion protection (prevents accidental branch deletion)
- Non-fast-forward protection (prevents force pushes)
- Optional CI status checks (if specified)
- Workflow files - Generates Dependabot configuration and auto-merge workflow
What You Need
- A GitHub repository with Dependabot enabled
ghCLI installed and authenticated- Write access to the repository
How to Use
Provide the repository name in owner/repo format. Optionally specify CI check names that must pass before auto-merge (e.g., build, test).
Example
Configure Dependabot auto-merge for tsubakimoto/turbo-train with CI checks: build, testIf CI checks are not specified, the ruleset will only enforce deletion and force-push protection.
Output
The skill generates:
- Repository configuration - Auto-merge and squash merge enabled
- Branch ruleset - Protection rules for the default branch
- Workflow file:
.github/workflows/dependabot-auto-merge.yml- Workflow for auto-merging patch/minor updates
Next Steps
After running this skill:
- The auto-merge workflow will be automatically committed and pushed
- Configure your own
.github/dependabot.ymlif needed (to avoid conflicts) - Dependabot will begin creating PRs according to your schedule
- Patch and minor updates will automatically merge once CI checks pass
- Major updates will require manual review
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

