updated coding standards
All checks were successful
Build, test and publish / verify (push) Successful in 4m43s
All checks were successful
Build, test and publish / verify (push) Successful in 4m43s
This commit is contained in:
16
docs/backend-review.md
Normal file
16
docs/backend-review.md
Normal file
@@ -0,0 +1,16 @@
|
||||
# Backend review companion
|
||||
|
||||
Use alongside `skills/code-review/SKILL.md` and `CODING_STANDARDS.md`.
|
||||
|
||||
Review changed code for intent-revealing comments, missing public-contract Javadoc,
|
||||
appropriate record use, defensive copying of mutable record components, and
|
||||
compatibility with APIs, JSON and persistence. Assess ambiguous `var` initializers
|
||||
and framework/lifecycle exceptions to field finality. Confirm architecture and
|
||||
injection decisions make sense for production and tests.
|
||||
|
||||
Read standards reports even when verification passes. Assess every review signal
|
||||
in changed code, including fan-out, public methods and record component counts.
|
||||
Record a rationale for retained signals in the S7 evidence or change description.
|
||||
Check narrowly scoped waivers against recorded maintainer agreement and reason.
|
||||
Never introduce blanket exclusions or weaken thresholds to pass a build.
|
||||
Do not repeat mechanical checks already enforced by tooling; verify their result.
|
||||
Reference in New Issue
Block a user