composer-update · git:20260415.08c2e3f · 2026-04-15 · sha256 be56656d57dfbf50

composer-update git:20260415.08c2e3fA

Immutable. This exact content never changes and is served at /api/v1/blob/be56656d57dfbf50.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_qe7tulxxo4jq7t6f/be56656d57dfbf50b16ddf997386d30b3bfabf7771939c0c858ccb53d1f869c0.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
- 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

```markdown
## Conflicts

No conflicts detected.

## Changelogs

### vendor/package (old → new)

- Breaking: ...
- New: ...
- Fix: ...

## Suggested Follow-up

- ...
```
---

## 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