---
title: "Comment by Erik D'Ercole on \"How to Organize Composer Scripts Effectively\" | Hashnode"
description: "For my Composer scripts, I prefer to use \"agnostic\" names: format, test, analyse, etc. Currently, they run Pint, Pest, PHPStan, but in the future each command c"
url: "https://hashnode.com/posts/how-to-organize-composer-scripts-effectively/666da502709d24f77df44105/comment/666eea2ae86e4a7a7de95aa4"
---

[Discussion](https://hashnode.com/posts/how-to-organize-composer-scripts-effectively/666da502709d24f77df44105)

Comment [How to Organize Composer Scripts Effectively](https://hashnode.com/posts/how-to-organize-composer-scripts-effectively/666da502709d24f77df44105)

[Erik D'Ercole](https://hashnode.com/@eleftrik)

[Jun 16, 2024](https://hashnode.com/posts/how-to-organize-composer-scripts-effectively/666da502709d24f77df44105/comment/666eea2ae86e4a7a7de95aa4)

For my Composer scripts, I prefer to use "agnostic" names: format, test, analyse, etc. Currently, they run Pint, Pest, PHPStan, but in the future each command could run another tool. This way, I don't need to change the command name.

[David Carr](https://hashnode.com/@dcblogdev)

[Jun 16, 2024](https://hashnode.com/posts/how-to-organize-composer-scripts-effectively/666da502709d24f77df44105/comment/666eea2ae86e4a7a7de95aa4#reply-666eefbea6644d5903d9b553)

that's a good strategy