agentsclimarketplace

Composer update

Skill pekral/cursor-rules/skills/composer-update

PHP and Laravel Cursor rules — coding standards, testing, and conventions for the Cursor editor. Install via Composer.

Install
npx -y skills add pekral/cursor-rules --skill composer-update

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when analyze composer update results, detect conflicts, and summarize changelogs of updated dependencies

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.1 KB, as published. Nobody here has run it

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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.