Document fix-and-check edit loop

This commit is contained in:
murashit 2026-06-30 23:23:47 +09:00
parent 332f11ab7e
commit 4ed285cedd

View file

@ -10,7 +10,7 @@ npm run fix
npm run check
```
Use this as the normal edit loop: make the change, run `npm run fix`, then run `npm run check`. `npm run fix` applies safe mechanical cleanup, and `npm run check` is the local preflight before review.
Use this as the normal edit loop: make the change, run `npm run fix`, then run `npm run check`. Treat `npm run fix` as trusted mechanical cleanup for formatting, import ordering, and Knip safe fixes; review the resulting diff at normal change-boundary checkpoints rather than after each tool adjustment.
Use focused scripts such as `npm run typecheck`, `npm run test`, or `npm run build` only when diagnosing a specific failure or when a full check would obscure the signal while iterating. Do not treat focused scripts as a substitute for the final `npm run check`. CI and release preflight run the same `npm run check` command as local development.