version-compare

Compare codebase versions and generate change reports with Git worktrees.

3|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/Linearl/linearleaf_skill_repo --skill version-compare
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-compare
Source: https://github.com/Linearl/linearleaf_skill_repo/tree/main/version_compare
Command: npx skills add https://github.com/Linearl/linearleaf_skill_repo --skill version-compare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to version comparison and change analysis, helping teams understand how releases diverge and what changes drive those divergences. It leverages a three-stage analysis plus Git worktree integration to safely compare old and new versions, generate change insights, and produce upgrade guidance and update logs.

Core Features & Use Cases

  • Three-Stage Analysis: Overall change analysis, core module deep comparison, and documentation review.
  • Git Worktree Integration: Safe dual-version workspaces to prevent disruption of the main repo.
  • Output Artifacts: Version comparison reports, module analyses, and update logs for release notes.
  • Use Case: Analyze a major release to identify breaking changes, affected modules, and necessary migration steps.

Quick Start

  • Describe your version range (e.g., V1.2 → V2.0) and the desired outputs (update log, compatibility report).
  • Enable the skill in your AI workflow and run a session to initialize worktrees and collect data.
  • Review the generated artifacts in the output directories.

Frequently Asked Questions about version-compare

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

FAQPage Schema
How do I analyze breaking changes and migration needs between two codebase versions?

Version comparison performs a three-stage change analysis across codebases to identify breaking changes, affected modules, and necessary migration steps. It applies systematic diff analysis to generate version comparison reports and update log drafts for release reviews.

Can I compare old and new release versions without disrupting my main git repository?

Yes, version comparison uses Git worktree integration to create safe dual-version workspaces. This prevents disruption of the main repository by isolating the old and new versions during the change analysis and documentation review process.

What is the best way to generate update logs and release notes from a major version diff?

Systematic version comparison generates update log drafts and version comparison reports by analyzing codebase divergences. It applies a three-stage workflow covering overall changes, core module deep comparison, and documentation review to produce release notes artifacts.

Does version comparison support upgrade planning for major framework releases?

Yes, version comparison supports upgrade planning by identifying how releases diverge and what changes drive those divergences. It generates upgrade guidance and compatibility reports by analyzing core module differences and necessary migration steps across version ranges.

How do I start a version diff analysis for a specific version range like V1.2 to V2.0?

Describe your version range and desired outputs, then run a session to initialize Git worktrees and collect data. The three-stage analysis workflow processes overall changes, core modules, and documentation to produce version comparison reports.

What files and artifacts are produced by a codebase change analysis workflow?

Codebase change analysis produces version_comparison_report.md and update_log_draft.md artifacts. These outputs capture version divergences, core module deep comparisons, and documentation review results for upgrade guidance and release notes.