From 8b8c45a5e46dc51a0905b3c77e50194de4e210a4 Mon Sep 17 00:00:00 2001 From: Taylor Mullen Date: Tue, 10 Mar 2026 20:57:56 -0700 Subject: [PATCH] docs: mandate exhaustive validation when fixing build errors or CI failures --- GEMINI.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/GEMINI.md b/GEMINI.md index f7017eab40..fe7db3bd42 100644 --- a/GEMINI.md +++ b/GEMINI.md @@ -51,9 +51,10 @@ powerful tool for developers. its long runtime, only run this at the very end of a code implementation task. If it fails, use faster, targeted commands (e.g., `npm run test`, `npm run lint`, or workspace-specific tests) to iterate on fixes before - re-running `preflight`. For simple, non-code changes like documentation or - prompting updates, skip `preflight` at the end of the task and wait for PR - validation.) + re-running `preflight`. When specifically fixing build errors, CI failures, or + addressing PR review feedback, exhaustive validation is mandatory to prevent + regressions. For simple, non-code changes like documentation or prompting + updates, skip `preflight` at the end of the task and wait for PR validation.) - **Individual Checks:** `npm run lint` / `npm run format` / `npm run typecheck` ## Development Conventions