coding-standards

Coding Standards

Use this Skill in exactly one of the following modes. Both modes derive compliance only from written standards that actually apply to the target files.

Implementation Guidance Mode

Use this mode when implementing, fixing, refactoring, or reviewing code unless the user explicitly requests a standalone coding-standards compliance audit.

• Before starting a read-only code review or making the first write in an implementation task, read the portions of CODE_OF_CONDUCT.md, repository-level and path-level AGENTS.md, Checkstyle, Spotless, and other written repository standards that actually apply to every affected file.
• Before the first write, record a compact applicable-rule checklist; group files governed by the same rules instead of repeating the checklist.
• For every affected Java file, read the Java naming and Lombok rules through EOF and add each applicable rule to the checklist.
• For every affected Java file, read the Java expression rules through EOF and add each applicable rule to the checklist.
• For every affected implementation artifact, read the defensive-code rules through EOF and add each applicable rule to the checklist.
• Determine whether each rule governs all existing code or only code that is new, modified, touched, submitted, or generated by Codex.
• Apply every applicable rule to each modified file within the task's authorized scope.
• After the last write, manually recheck the effective task delta and only the surrounding declarations needed to evaluate every applicable checklist rule.
• For Java, explicitly verify every applicable CODE_OF_CONDUCT.md coding rule, including declaration order; when a method uses private helpers, verify that those helpers immediately follow the caller and appear in the caller's call order, regardless of the caller's visibility.
• For Java, explicitly verify every applicable Java naming and Lombok rule against the effective task delta and the surrounding declarations needed to resolve semantic applicability.
• For Java, explicitly verify every applicable Java expression rule against the effective task delta and the declarations needed to resolve named constants.
• Explicitly verify every applicable defensive-code rule against the effective task delta and the contracts, producers, consumers, and supported paths needed to determine whether each defensive construct has qualifying evidence.
• Treat passing Checkstyle and Spotless as evidence only for the rules those tools enforce; neither result replaces the manual recheck.
• A later write invalidates final-check evidence only for affected files and rules; recheck those portions before verification or handoff.
• Do not create rules from personal preference, general clean-code principles, or nearby code.
• Do not scan for or report pre-existing violations outside the current task scope.
• Run the applicable formatting and standards checks required by the repository workflow.
• Do not run apply, format, or another file-modifying command unless the current task authority and repository rules authorize every possible write.
• Do not build a complete file inventory or perform physical-line accounting in this mode.