laravel-dependency-tree-upgrade

You can audit composer.lock dependencies by scanning first-party and organization packages to identify which support the current Laravel version but not the next. This skill automates that dependency tree analysis to surface upgrade blockers proactively.

Automating Jira ticket creation for Laravel upgrades involves generating missing tickets in an existing or new epic and wiring blocker links in the correct sequential order. This skill pre-fills framework package details based on Laravel conventions to streamline the process.

Yes, you can upgrade both first-party and organization Composer packages. The skill scans your composer.lock to surface constraints for both package types, applying Illuminate conventions to determine if they support the target Laravel version before generating tracking tickets.

You need to supply the target Laravel version and a Jira epic identifier. The skill applies Laravel-specific conventions and pre-fills framework package details automatically, scanning your composer.lock to map out the required upgrade order and wiring the relevant blockers.

Mapping out Laravel framework package constraints requires scanning composer.lock to detect version blockers and organizing them sequentially. This skill audits dependencies, applies Illuminate constraint conventions, and wires Jira blocker links to establish the correct upgrade order.