agentleFS
MrPunyapalMrPunyapal/laravel-auditor/.agents/skills/package-compatibility/SKILL.md

package-compatibility

Skill78 starsChanged 3 months agoMITView on GitHub

Use this skill when reviewing Laravel package compatibility across composer constraints, PHP versions, Laravel versions, Testbench versions, dependency stability lanes, Windows CI, or matrix-sensitive code and workflow changes.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep package code, dependencies, and workflows compatible with the supported Laravel 12/13 and PHP 8.3+ matrix.

    line 13
  2. Very specific:

    Read composer.json first to determine PHP, Laravel, and Testbench constraints.

    line 17
  3. Distinctive:

    Check changed code against Laravel 12/13 APIs and PHP 8.3+ syntax before adopting newer framework or language features.

    line 18
  4. Distinctive:

    When changing dependencies, confirm constraints still allow the intended Laravel and Testbench versions.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Package Compatibility

Primary Goal

Keep package code, dependencies, and workflows compatible with the supported Laravel 12/13 and PHP 8.3+ matrix.

Workflow

  1. Read composer.json first to determine PHP, Laravel, and Testbench constraints.
  2. Check changed code against Laravel 12/13 APIs and PHP 8.3+ syntax before adopting newer framework or language features.
  3. Review .github/workflows/tests.yml for dependency stability lanes, prefer-lowest coverage, prefer-stable coverage, and Windows concerns.
  4. When changing dependencies, confirm constraints still allow the intended Laravel and Testbench versions.
  5. Validate with the smallest local command available, then rely on CI for full OS and dependency matrix coverage.

References

  • composer.json
  • .github/workflows/tests.yml
  • phpstan.neon.dist
  • tests/
  • workbench/

Examples

  • Review a new Laravel API call by checking whether it exists in Laravel 12 and Laravel 13 before merging it into shared package code.
  • Review a dependency bump by checking Composer constraints, Testbench constraints, prefer-lowest behavior, and Windows path assumptions.

Anti-Patterns

  • Assuming the latest local dependency version represents the whole support matrix.
  • Adding PHP syntax or Laravel APIs that exceed composer.json constraints.
  • Ignoring Windows path separators, executable assumptions, or shell-only syntax in tests and workflows.
  • Removing dependency stability lanes because they are slower than a single happy path.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.