composer-update · git:20260522.4d957fd · 2026-05-22 · sha256 0a8c3eb52225c63f
composer-update git:20260522.4d957fdA
Immutable. This exact content never changes and is served at /api/v1/blob/0a8c3eb52225c63f.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_qe7tulxxo4jq7t6f/0a8c3eb52225c63f1eb5a2deec7c796ff972c00f5913f3b6519972ee3b8e84ee.json
Then /plugin install composer-update@markdownregistry-qe7tulxxo4jq7t6f in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
---
name: composer-update
description: Use when analyze composer update results, detect conflicts, and
summarize changelogs of updated dependencies
license: MIT
metadata:
author: Petr Král (pekral.cz)
---
# Composer Update
## Purpose
Analyze dependency updates after `composer update`, detect conflicts, and summarize relevant changes.
---
## Constraints
- Apply @rules/php/core-standards.mdc
- Apply @rules/php/dependency-selection.mdc — this skill primarily *bumps* existing packages (rule out of scope per its *Scope* section), but a bump frequently uncovers an upstream that has been archived or marked abandoned. When that happens, re-run the Activity gate + Compatibility gate against the suggested replacement (or against a fresh search if no replacement is documented) before recommending the migration. Never silently keep an archived / abandoned package in the lockfile just because the bump compiles.
- Output Markdown only
---
## Execution
### 1. Update Context
- Use output from `composer update` if available
- Otherwise compare current `composer.lock` with the previous version
### 2. Detect Updated Packages
- List all added or changed packages
- Include version changes: `old → new`
### 3. Conflict Detection
- Identify dependency conflicts from:
- composer output
- version constraint mismatches (`composer.json` vs `composer.lock`)
- Summarize conflicts clearly (package → reason)
- If none: state "No conflicts detected"
### 4. Changelog Extraction
For each updated package:
- Prefer:
- `vendor/<package>/CHANGELOG*`
- Fallback:
- repository releases (GitHub/GitLab)
- package homepage
- Extract:
- breaking changes
- new features
- important fixes
- If unavailable:
- state "No changelog found"
### 5. Suggested Follow-up
- Recommend relevant checks:
- run tests
- `composer validate`
- `composer audit`
---
## Output Format
Use the template defined in `templates/update-report.md`.
---
## Principles
- Focus on impactful changes, not noise
- Highlight breaking changes first
- Prefer local sources over remote
- Be concise and actionable
- Highlight security-related changes when present