setup-deps

Generates and re-syncs Dependabot config and dependency automation workflows from detected repo ecosystems.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/Sassy-Dog/sassydog-skills --skill setup-deps-sassy-dog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-deps
Source: https://github.com/Sassy-Dog/sassydog-skills/tree/main/skills/setup-deps
Command: npx skills add https://github.com/Sassy-Dog/sassydog-skills --skill setup-deps-sassy-dog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve? Dependabot PRs often fail silently: lanes point at directories with no manifests, lockfiles go stale under frozen-lockfile CI, and App-token workflows break in public repos where org secrets cannot resolve. This Skill detects a repo's actual ecosystems and renders a correct, grouped .github/dependabot.yml plus the supporting auto-merge and lockfile-sync workflows, then validates every lane against the repo before writing. ## Core Features & Use Cases - Ecosystem detection probe: Scans tracked repo files to detect npm, bun, cargo, gradle, pub, nuget, pip, gomod, swift, docker, and cocoapods, reporting the exact directory of each manifest and flagging lockfile risk. - Scripted render with post-render validation: Renders one Dependabot lane per (ecosystem, directory) pair from templates, then asserts every declared directory actually holds its manifest and reports diverged lanes instead of silently dropping them. - Merge-gate and visibility preconditions: Probes branch protection, rulesets, and repo visibility before rendering auto-merge or lockfile-sync workflows, refusing to emit App-token workflows into public repos. - Use Case: A monorepo with npm workspaces, a Flutter app, and a Rust workspace asks to "set up Dependabot" — the Skill detects each ecosystem at its real directory, renders grouped lanes, and skips the auto-merge workflow because the repo is public, reporting the manual lockfile path instead. ## Quick Start Ask the agent to set up Dependabot and dependency auto-merge for this repository, and it will detect the stack, render the config, and validate it before writing.

Frequently Asked Questions about setup-deps

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

FAQPage Schema
How do I set up Dependabot for a monorepo with multiple package.json files?

Dependabot reads the manifest at each directory entry and does not recurse, so a monorepo needs one lane per manifest location. This Skill's detection probe reports every package.json directory and renders one grouped lane per directory automatically.

Why do Dependabot PRs fail CI with frozen-lockfile errors in a bun repo?

Dependabot's npm ecosystem updates package.json but cannot write bun.lock, so frozen-lockfile installs reject the PR. The native bun ecosystem handles text bun.lock directly; binary bun.lockb repos need the lockfile-sync workflow this Skill renders.

Can Dependabot auto-merge work in a public GitHub repository?

Not with org-level App secrets at private visibility, which exclude public repos in both the Actions and Dependabot stores. The Skill refuses to render App-token workflows into public repos and reports the manual regenerate-and-push path instead.

How do I stop Dependabot from flooding my repo with PRs?

Configure groups with both applies-to: version-updates and applies-to: security-updates entries per ecosystem. A group without applies-to covers version updates only, silently leaving security PRs ungrouped, which the rendered template avoids by default.

Will re-running the generator overwrite my hand-written dependabot.yml?

No. The Skill reconciles only files carrying its generated-by marker and reports hand-written files without touching them. It also accepts legacy marker namespaces from earlier plugin versions so pre-rename files still reconcile.