From 4ed285cedd531d5a072f322060d3c1ea1ef5fe42 Mon Sep 17 00:00:00 2001 From: murashit Date: Tue, 30 Jun 2026 23:23:47 +0900 Subject: [PATCH] Document fix-and-check edit loop --- docs/development.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/development.md b/docs/development.md index bd5a8e09..eedd0477 100644 --- a/docs/development.md +++ b/docs/development.md @@ -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.