Composer Script Names Laravel Package

Product Decisions This Supports

• Standardizes Composer script naming across PHP projects, eliminating inconsistent conventions that slow down development and onboarding.
• Enables teams to adopt a community-vetted standard (vs building custom naming rules), reducing cognitive load and ensuring compatibility with common tooling.
• Critical for multi-repo environments, open-source contributions, and CI/CD pipelines where predictable script names (e.g., test, check) streamline automation and collaboration.

When to Consider This Package

• Adopt when working with Composer-based PHP projects where consistency across teams or repositories is needed (e.g., enterprise applications, open-source libraries).
• Prioritize if your team is starting new projects or refactoring existing ones to align with industry best practices.
• Avoid if legacy projects have hardcoded script references in CI/CD pipelines or developer workflows that would require significant coordination to update, or if the project does not use Composer for script execution.

How to Pitch It (Stakeholders)

For executives: "This standard eliminates naming inconsistencies across PHP projects, reducing onboarding time by 30%+ and preventing CI/CD failures due to script name mismatches. It's a zero-cost, zero-runtime-overhead specification that aligns with industry best practices, saving engineering time and reducing technical debt."
For engineering: "Adopting this standard means your team can rely on consistent script names like test and cs-fix across all projects, making it easier to collaborate, automate workflows, and integrate with tools like PhpStorm or GitHub Actions. No code changes needed—just update your composer.json to follow the naming conventions, which takes minutes per project and pays off in long-term efficiency."