What problem does it solve?
This Skill reduces the risk and reviewer effort of upgrading project dependencies by locating a safe target version, summarizing upstream changes, assessing repository-specific impact, updating pins and lockfiles, and opening a documented pull request so reviewers can approve with confidence.
Core Features & Use Cases
- Ecosystem detection: Detects whether a package is a Python or JavaScript dependency by scanning requirements files, pyproject.toml, package.json, and lockfiles.
- Safe version selection: Applies rules to avoid brand-new major releases and very recent releases, preferring stable targets that are at least a week old unless a safe patch is available.
- Changelog and impact analysis: Locates upstream changelogs and GitHub releases, summarizes notable changes, and searches the codebase for imports/usages to assess upgrade risk.
- Automated upgrade workflow: Updates version pins, regenerates lockfiles when appropriate, creates a dependency-upgrade branch, and prepares a PR with a clear risk assessment and changelog summary.
Quick Start
Run the dependency-upgrade skill with the package name to detect the ecosystem, pick a safe target version, summarize notable changes and risk, update pins and lockfiles, and open a pull request.