Rules Hub
Coding Rules Library
← Back to all rules
Rule priority, scope & exceptions
Use this to align rules with the senior-level structure (P0/P1/P2, scope, exceptions/tradeoffs).
fullstack ruleP2universalStack: universal
processpull-requestdocumentationreview
Make the PR template descriptive with a pre-merge checklist
Replace one-word headings with explicit questions (what/why/how/testing) and add a 'remember to check' list (tests pass, description written, shared functions tested) so reviewers can reject incomplete PRs fast.
PR: hegnar-forum-web · org-mining-hist-2026-06Created: Jun 20, 2026
Bad example
Old codemarkdown
| 1 | ## What? |
| 2 | ## Why? |
| 3 | ## How? |
| 4 | ## Testing? |
Explanation (EN)
Objašnjenje (HR)
Good example
New codemarkdown
| 1 | ## What is this PR doing? |
| 2 | ## Why are we solving this issue? |
| 3 | ## How is the solution implemented? |
| 4 | ## Screenshots / video (optional) |
| 5 | ## How should this be tested? |
| 6 | ## Anything else? |
| 7 |
|
| 8 | --- |
| 9 | Remember to check: |
| 10 | - Tests should pass |
| 11 | - Commits should be tagged |
| 12 | - Description must be written |
| 13 | - Shared functions must have tests |
Explanation (EN)
Objašnjenje (HR)