Rules Hub
Coding Rules Library
Rule priority, scope & exceptions
Use this to align rules with the senior-level structure (P0/P1/P2, scope, exceptions/tradeoffs).
Keep scratch/investigation artifacts out of feature PRs
Don't commit ad-hoc audit/investigation/scratch docs into a feature PR; keep the change scoped and remove accidentally-committed files.
Bad example
| 1 | // committed alongside the feature change: |
| 2 | // src/feature.ts |
| 3 | // OXLINT_RULES_AUDIT.md <- ad-hoc investigation notes |
Explanation (EN)
Bundling unrelated investigation/audit notes into a feature PR pollutes the diff, confuses reviewers, and leaves stray files in the repo.
Objašnjenje (HR)
Ubacivanje nepovezanih biljeski istrazivanja/revizije u feature PR zagaduje diff, zbunjuje recenzente i ostavlja zalutale datoteke u repozitoriju.
Good example
| 1 | // committed alongside the feature change: |
| 2 | // src/feature.ts |
| 3 | // investigation notes kept in an issue/wiki, not the repo diff |
Explanation (EN)
Keeping the PR limited to files that belong to the change makes review focused; scratch notes live in an issue, doc, or are deleted before pushing.
Objašnjenje (HR)
Ogranicavanje PR-a na datoteke koje pripadaju promjeni cini recenziju fokusiranom; biljeske idu u issue, dokument ili se brisu prije pusha.
Exceptions / Tradeoffs (EN)
Intentional, reviewed documentation that is genuinely part of the change is fine to include.
Iznimke / Tradeoffi (HR)
Namjerna, recenzirana dokumentacija koja je stvarno dio promjene moze se ukljuciti.