Skip to content

docs: add 'never ignore lint warnings' working principle #390

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
carlos-alm merged 2 commits into from
Mar 9, 2026
+7 −0
Merged

docs: add 'never ignore lint warnings' working principle #390

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5d283a4
docs: add 'never ignore lint warnings' working principle
carlos-alm Mar 9, 2026
89f70cd
Consistency change on CLAUDE.md
carlos-alm Mar 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Comment thread
carlos-alm marked this conversation as resolved.
Outdated
* Run `npm run lint` after editing code and review the output — do not assume warnings are spurious