Ergonomics of `--no-write-lock-file`

In a repo that has no flake.lock checked in (nor does it typically have one in the working directory and ignored), I find it inconvenient to add --no-write-lock-file to various invocations. Even worse, forgetting to do so and having to git rm -f flake.lock afterwards.

I set up a shell with a check script that is nix flake check --no-write-lock-file but that’s not the only nix command that would by default write a lock file.

Any bright ideas to improve ergonomics in this situation, please?