On the bundled sample: 10 findings (4 errors, 6 warnings) in 1 file from 14 rules, including “^7.4 || ^8.0” and a platform pin to PHP 7.4.

Who it’s for
PHP library maintainers and Laravel/Symfony teams about to tag a release or raise their PHP floor.

What breaks, and when
PHP 7.4 reached end of life 2022-11-28 and 8.1 on 2025-12-31; 8.2 follows 2026-12-31. A name that fails the schema pattern stops composer validate.

What you get
• SKILL.md, an offline Node scanner and the 14-rule table
• file:line, severity and the end-of-life date

See it first
The real output of the bundled example is on getreadystack.com/skills/composer-json-php-eol-check/ — free, no sign-up, so you see what it finds before you pay.

Install in 30 seconds
Unzip into ~/.claude/skills/, then ask Claude Code: “We want to tag a new release of this PHP package. Is composer.json ready, and which PHP versions do we still claim to support? Don’t edit anything yet.”. Needs Node 16+.

What it does not do
It does not run Composer or resolve dependencies; it reads composer.json text only.

FAQ
Q: How is this different from asking Claude without the skill?
A: The skill carries a dated rule table and a scanner that reads every file, so Claude quotes the exact date and line instead of guessing from memory.
Q: How do I get the files?
A: In your Whop library after paying: the lesson “composer-json-php-eol-check.zip”.