From 5d283a4de927f8a03d2e340a6f9e85ef28918243 Mon Sep 17 00:00:00 2001 From: carlos-alm <127798846+carlos-alm@users.noreply.github.com> Date: Mon, 9 Mar 2026 01:58:42 -0600 Subject: [PATCH 1/2] docs: add 'never ignore lint warnings' working principle --- CLAUDE.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index fb22fc2e..d8a053ae 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -190,3 +190,10 @@ Requires Node >= 20. * If something goes sideways, STOP and re-plan immediately – don't keep pushing * Use plan mode for verification steps, not just building * Write detailed specs upfront to reduce ambiguity + +### 2. Never Ignore Lint Warnings + +* Never silently skip or dismiss linting/formatting warnings — always check whether they are relevant to the current change +* If a warning fires on code you touched, fix it +* If a warning fires on code you didn't touch, mention it to the user but don't fix it (per the "don't clean up other sessions' files" rule) +* Run `npm run lint` after editing code and review the output — do not assume warnings are spurious From 89f70cd9e7df565f15d9ecca4a7b82b0e31e26d4 Mon Sep 17 00:00:00 2001 From: carlos-alm <127798846+carlos-alm@users.noreply.github.com> Date: Mon, 9 Mar 2026 02:10:03 -0600 Subject: [PATCH 2/2] Consistency change on CLAUDE.md Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> --- CLAUDE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CLAUDE.md b/CLAUDE.md index d8a053ae..505d533d 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -195,5 +195,5 @@ Requires Node >= 20. * Never silently skip or dismiss linting/formatting warnings — always check whether they are relevant to the current change * If a warning fires on code you touched, fix it -* If a warning fires on code you didn't touch, mention it to the user but don't fix it (per the "don't clean up other sessions' files" rule) +* If a warning fires on code you didn't touch, mention it to the user but don't fix it (per the "Do not clean up lint/format issues in files you aren't working on" rule in Parallel Sessions) * Run `npm run lint` after editing code and review the output — do not assume warnings are spurious