agentleFS
MicrosoftKnown publishermicrosoft/dbt-fabricspark/.github/skills/compact-dependabot/SKILL.md

compact-dependabot

Skill72 starsChanged 5 months agoMITView on GitHub

Compact open Dependabot PRs into a single branch, run CI, and open a consolidated PR.

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Distinctive:

    If git apply fails for any section, split the patch by PR section and apply individually.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Compact Dependabot

Merge all open Dependabot dependency bumps into one PR that passes CI.

Steps

  1. Fetch the diffs — run the TypeScript tool to download Dependabot PR diffs:

    npx tsx tools/gh-automation/compact-dependabot.ts

    This writes dependabot-diffs.patch in the repo root.

  2. Study the patch file — read dependabot-diffs.patch to understand what dependencies are being bumped and across which ecosystems (npm, uv/pip, etc.).
  3. Reuse the existing branch the user is already on, UNLESS it's on main, in that case, create a new branch from main:

    git fetch origin main
    git checkout -b chore/compact-dependabot origin/main
  4. Apply the diffs — apply each PR's diff from the patch file. The patch file contains sections separated by comment headers (# PR #<number>: <title>). Apply them with:

    git apply dependabot-diffs.patch

    If git apply fails for any section, split the patch by PR section and apply individually. Resolve any conflicts manually.

  5. Install updated dependencies — run the appropriate install commands for each ecosystem that changed:

    • npm: npm install
    • uv/pip: uv lock or uv sync
  6. Run build:

    npx nx affected --base=origin/main -t build --parallel=3 --configuration=ci --output-style=stream --verbose
  7. Run lint:

    npx nx affected --base=origin/main -t lint --parallel=3 --configuration=ci --verbose --output-style=stream --verbose
  8. Fix failures — if build or lint fail, read the errors and fix them. Re-run until green.
  9. Commit and push:

    git add -A
    git commit -m "chore: compact dependabot bumps"
    git push origin chore/compact-dependabot
  10. Open a PR:

    gh pr create --title "chore: compact dependabot bumps" --body "Consolidates open Dependabot PRs into a single change." --base main

    Capture the new PR URL from the output.

  11. Close the Dependabot PRs — for each Dependabot PR that was included, add a comment linking to the new PR, then close it:

    gh pr comment <number> --body "Superseded by <new-pr-url>"
    gh pr close <number>
  12. Clean up — delete the patch file:

    rm dependabot-diffs.patch

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.