dependency-update

Researches, classifies, and validates dependency updates across every manifest in a polyglot repository.

23|1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Alexey-Lukin/silken_net --skill dependency-update-alexey-lukin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-update
Source: https://github.com/Alexey-Lukin/silken_net/tree/main/.claude/skills/dependency-update
Command: npx skills add https://github.com/Alexey-Lukin/silken_net --skill dependency-update-alexey-lukin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Updating dependencies in a polyglot repository is risky: changelogs go unread, transitive bumps slip in, security alerts live in channels no outdated-command covers, and a green CI suite can mask a breaking change. This Skill provides an executable playbook that forces per-dependency research, classification, and domain-appropriate validation before any bump is merged. ## Core Features & Use Cases - Per-domain inventory and validation recipes: Covers Ruby gems, Ruby itself, bundler, CI workflow actions, JS/importmap vendored assets, conda ML and in-silico environments, firmware C submodules, Terraform providers, .NET NuGet pins, Solidity/Foundry contracts, the subgraph npm toolchain, and Docker runtime images. - Structured core loop: Read open Dependabot security alerts first, inventory what is outdated, research the exact version's changelog, classify as security/breaking/behavior/routine, validate with the domain's gate, and capture the research in the commit body. - 46 hard-won gotchas: An indexed companion file (gotchas.md) documents real incidents such as release-age quarantine, transitive caps, masked breaking passengers, and stale green checks. - Use Case: Run a full dependency sweep before a release: check open security alerts, run bundle outdated and per-domain inventory commands, research each candidate version, apply the release-age quarantine, validate with the domain's test gate, and commit each bump with its research in the commit body. ## Quick Start Ask the assistant to run the dependency sweep and update the outdated gems, researching each changelog and validating with the full test suite before committing.

Frequently Asked Questions about dependency-update

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

FAQPage Schema
How do I safely update dependencies in a polyglot repository?

Follow the core loop: check open Dependabot security alerts first, inventory outdated packages per domain, read each target version's changelog, classify the change as security, breaking, behavior, or routine, then validate with the domain's test gate before committing with the research in the commit body.

What is release-age quarantine for dependency updates?

A version younger than about seven days waits before adoption, because hijacked-maintainer and malicious-postinstall compromises are usually caught within days. The quarantine is discharged by a needed security fix or by an examined publisher profile such as trusted publishing and no postinstall scripts.

Why can a green CI suite still hide a breaking dependency bump?

A green suite can be masked, for example when a spec patches the gem's own API or a library like Oj replaces JSON.parse at runtime. After any major bump, grep specs for singleton method redefinitions and probe the call path with the mask absent.

Does Dependabot cover all dependency pins in a repository?

No. Dependabot pins wrappers but never payload pins inside actions, hand-pinned vendored binaries, vendored front-end assets, or ecosystems with no configured entry such as NuGet central pins. Those must be inventoried and bumped by hand.

How should I validate a Terraform provider or Solidity toolchain bump?

Terraform providers require reading the per-major upgrade guide, then terraform validate and fmt, with plan gated on CI credentials. Solidity bumps are validated locally with forge test and fmt, while slither analysis runs only in CI.