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).

PriorityP2 — style, consistency, readabilityScopeUniversal — language-agnostic, broadly applicable

Exceptions / tradeoffs (EN)Iznimke / tradeoffi (HR)

fullstack ruleP2universalStack: Git

gitcommitsconventionsprocess

Adopt Conventional Commits for commit messages

Format commit messages as type(scope): description (e.g. feat(docs): update template), optionally referencing a ticket, so history is structured and tooling-friendly.

PR: vinify-frontend · org-mining-hist-2026-06Created: Jun 19, 2026

Bad example

Old codetext

1	`updated the pull request template`

Explanation (EN)

Objašnjenje (HR)

Good example

New codetext

1	`feat(docs): update pull request template`
2
3	`refs: TICKET-123`

Explanation (EN)

Objašnjenje (HR)

Login required