agentleFS
SHREESHMANSHREESHMAN/lineupify/.claude/skills/dependabot-triage/SKILL.md

dependabot-triage

Skill1 starsChanged 2 months agoMITView on GitHub

Review and land Dependabot pull requests on Lineupify: which to merge, how to handle conflicting adjacent bumps, majors that need code changes, and the ignore rules. Use when asked to check PRs, workflow runs, or dependency updates.

  • Commits and pushes

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. hmislk/hmis★ 244same name
    2. jaskirat1616/grok-skills★ 22same name
    3. aki77/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep package-lock.json committed.

    line 42

≈ “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

Dependabot triage

Config: .github/dependabot.yml. Weekly. Groups: eslint (eslint + @eslint/*, always together because they peer-depend on each other), dev-dependencies-minor (minor/patch of other dev deps). Majors of other packages arrive one PR each. Ignored: TypeScript majors (typescript-eslint pins a range and lags), @types/node majors (types track the Node 20 floor in engines).

Look

gh pr list --json number,title,mergeable --jq '.[] | "#\(.number) \(.mergeable) \(.title)"'
gh run list --limit 10 --json status,conclusion,displayTitle,event --jq '.[] | "\(.status) \(.conclusion // "-") [\(.event)] \(.displayTitle)"'
gh run view <id> --log-failed | grep -E "npm error|error TS|✖|problems"

Decide

  • GitHub Actions bumps (checkout, setup-node): merge when CI is green. gh pr merge <n> --squash --delete-branch.
  • Runtime deps (open, zod, @modelcontextprotocol/server): read the PR body for breaking notes; open and the SDK matter to users. Merge when green and the notes are benign; for the MCP SDK also run node test/smoke/mcp-stdio.mjs after npm run build.
  • Dev majors (ESLint, Vitest): CI is the judge, but read the notes. ESLint majors add default rules; the fixes are usually small and worth making on main (that is how ESLint 10 landed: two rule fixes, then the bump).
  • Failing at npm ci with ERESOLVE: a peer range conflict (typically TypeScript vs typescript-eslint). Close the PR; the ignore rule should have caught it, so check the config.

Conflicts between two Dependabot PRs

They edit adjacent lines (e.g. checkout and setup-node in the same workflow). Merge one, then either comment @dependabot rebase on the other, or apply the bump on main yourself and close the PR with a comment naming the commit. Applying directly is faster and deterministic:

git pull --ff-only origin main
sed -i 's#actions/setup-node@v4#actions/setup-node@v7#g' .github/workflows/*.yml
git commit -am "Bump actions/setup-node from 4 to 7" && git push
gh pr close <n> --comment "Applied on main in <sha>"

After merging

git pull --ff-only origin main && npm ci && npm test

Keep package-lock.json committed; never npm install a dep in the same commit as unrelated code.

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.