team-coding-standards

Apply a fixed naming rulebook during pull request review: camelCase for variables and functions, UPPER_SNAKE_CASE for constants, PascalCase for classes and interfaces, and an underscore prefix for private fields. The reviewer flags violations like my_variable or max_retries with corrected forms.

Check only the added lines in the diff and verify every public function, method, class, or exported variable has a JSDoc block. Minimum coverage includes a description, an @param tag per parameter, and an @returns tag; missing JSDoc on public APIs is treated as a high-priority violation.

Review only lines marked with +, meaning new or changed code. Deleted lines marked with - are excluded from review since removed code no longer affects the codebase.

Require a why-comment when logic is non-obvious, using the criterion that a comment is needed if the next developer would spend more than 30 seconds understanding the code. Comments should explain intent, not restate what the code does.

Rule-based review only catches violations covered by the defined standards, such as naming, JSDoc, and comments. It does not detect logic bugs, security issues, or architectural problems, so it should complement rather than replace human review and testing.