composer-update

Analyze Composer dependency updates and generate changelog impact reports.

Updated Aug 15, 2025
One-click install
npx skills add https://github.com/pekral/pekral.cz --skill composer-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: composer-update
Source: https://github.com/pekral/pekral.cz/tree/main/.claude/skills/composer-update
Command: npx skills add https://github.com/pekral/pekral.cz --skill composer-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Composer updates can silently introduce breaking changes or dependency conflicts, and it is time-consuming to figure out what actually changed and why.

Core Features & Use Cases

  • Updated dependency detection: Identifies added or changed packages and reports version transitions.
  • Conflict detection and explanation: Flags conflicts from composer output and mismatches between composer.json constraints and composer.lock.
  • Changelog extraction for impact: Pulls breaking changes, new features, and important fixes from package changelogs or release sources, when available.

Quick Start

Ask the skill to analyze your composer update results (or compare your current composer.lock to the previous version) and produce an update report using the project template.

Frequently Asked Questions about composer-update

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

FAQPage Schema
How do I check for breaking changes after a composer update?

To detect composer dependency conflicts, compare your composer.json constraints against the composer.lock file and analyze composer output. This identifies mismatches and highlights version transition issues that may cause application errors.

What is the best way to summarize PHP dependency updates from a lockfile?

Summarizing PHP dependency updates involves parsing old to new version transitions from changed packages. This analysis compiles breaking changes, new features, and important fixes into a structured report to evaluate upgrade risks.

Can I compare two composer.lock snapshots to understand upgrade risk?

Yes, you can compare a current composer.lock against a prior lockfile snapshot to understand upgrade risk. This comparison detects added or changed packages and extracts changelog impact to highlight breaking changes and fixes.

Why does my composer update show a conflict between composer.json and composer.lock?

A conflict between composer.json and composer.lock occurs when dependency constraints do not match the resolved versions. Analyzing these mismatches flags version transition issues and helps extract relevant package changelog impact.