Extend Laravel's Default Commands or Block them on production?

There are a few Artisan commands that I do not want to be run on production. For example, I would like to block the use of php artisan migrate:reset on production.

I would like to completely block this command OR Update the template artisan uses when running php artisan make:migration. The reason for updating the template is so I can make the template extend a different Class instead of the Migration class. In this new class I can inject my custom protection logic. I just don't want other developers using the artisan command and extending the wrong class.

via Chebli Mohamed