devCommand

It won’t let you wipe the wrong database.

The worst commands make you type the database name. The risky ones ask first, showing the exact command, the folder and the database. However the command was started.

Free for everyone · macOS 14 Sonoma or later · Apple silicon and Intel

1

Type to confirm

migrate:fresh, migrate:refresh, migrate:reset, db:wipe and key:generate need the database name typed.

2

Asked first

migrate, rollback, db:seed, queue:flush, queue:forget, composer update and artisan down ask before running.

3

Reads the command line

migrate asks; migrate:status doesn’t. The check is on what will actually run.

4

No way around it

Button, search, pin, your own command or --run from a script — the same rules apply.

01

See exactly what will happen

The confirmation shows the full command, the project folder and the database it will touch.

  • Database read from .env
  • The folder, spelled out
  • Nothing runs until you say so
02

Search can’t skip it

Found migrate:fresh with ⌘K? Same question, same typed name.

  • Palette runs are checked
  • Pinned runs are checked
  • Scripted runs are checked
03

Health first

Debug on in production, a missing .env or keys missing from it — flagged before they bite.

  • File-only checks
  • One-click fixes
  • Nothing runs without you

The small things

Details that add up.

Shows the database

Read from the project’s .env, so you know which one.

Your own commands too

Turn on confirmation with your own message.

Sequences too

Every step is checked.

Clear wording

Plain sentences, not warnings in capitals.

Button or script

The same check, however the command was started.

Status is left alone

Read-only commands like migrate:status never ask.

Free, and ready when you are.

No account, no licence key. Point devCommand at ~/Sites and press your first command.

macOS 14 Sonoma or later · Apple silicon and Intel · Version 1.0