dependency-changes

Analyze Maven/Gradle dependency version changes and fetch release notes, changelogs, and GitHub releases.

23|2|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/kirich1409/krozov-ai-tools --skill dependency-changes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-changes
Source: https://github.com/kirich1409/krozov-ai-tools/tree/main/plugins/maven-mcp/plugin/skills/dependency-changes
Command: npx skills add https://github.com/kirich1409/krozov-ai-tools --skill dependency-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Show what changed between two versions of a Maven/Gradle dependency — fetches release notes, changelog entries, and GitHub releases for the version range.

Core Features & Use Cases

  • Compare two artifact versions and surface release notes, changelogs, and GitHub releases.
  • Handle explicit version ranges or prompts that imply a range; supports multiple artifacts when provided.
  • Provide direct links and concise summaries to guide upgrades.

Quick Start

Provide coordinates and versions, for example io.ktor:ktor-client-core from 2.3.0 to 3.1.3, to see what changed.

Frequently Asked Questions about dependency-changes

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

FAQPage Schema
How do I check what changed between two Maven or Gradle dependency versions?

To check dependency version changes, provide the artifact coordinates and the target version range. The tool fetches release notes, changelogs, and GitHub releases for that Maven or Gradle artifact.

What is a dependency version change analysis and when do I need it?

Dependency version change analysis surfaces release notes and changelog entries between two versions of an artifact. You need it before upgrading libraries to understand breaking changes and new features.

Can I compare multiple artifacts or more than two versions at once?

You can analyze multiple artifacts when provided, but version ranges are limited to two versions per artifact. The tool processes explicit coordinates and fetches corresponding GitHub releases.

Does this work with both Maven and Gradle build configurations?

Yes, it supports Maven and Gradle artifacts by parsing standard coordinates. It integrates with check-deps outputs when available to surface release notes and changelogs.

What format should I use to provide artifact coordinates for version comparison?

Provide standard Maven or Gradle coordinates with explicit version ranges, such as io.ktor:ktor-client-core from 2.3.0 to 3.1.3. The tool parses these to fetch release notes.

What are the limitations when analyzing dependency release notes?

Analysis is scoped to two-version ranges per artifact and depends on available GitHub releases or changelogs. It provides concise summaries and direct links rather than full code diffs.