code-hygieneKeep a diff minimal and self-explanatory — no comments restating code, no dead code, no speculative abstraction, no unrelated churn, no redundant tests. Use when reviewing your own diff before saying done, and before adding a comment, docstring or test.
completion-gateDefinition of done — never commit until asked; before saying done, prove build, full tests, static analysis, language standards, meaningful coverage, hygiene and Sonar with evidence. Use when finishing any code change, before reporting it done, and after every fix made during the check.
sonar-quality-gateDrive the SonarQube/SonarCloud new-code quality gate to green — bugs, vulnerabilities, smells, hotspots, duplication, coverage — without suppressing findings; report honestly if Sonar is unreachable. Use when the completion gate reaches Sonar or a pipeline's Sonar gate fails.