document

To add code documentation explaining decisions, analyze the codebase to identify non-obvious business logic and generate concise, rationale-focused comments that clarify intent while preserving existing structure.

Generating code comments for onboarding involves creating documentation maps that explain non-obvious logic in plain language, reducing cognitive load for new contributors by focusing on why the code exists rather than what it does.

To clean up code comments and remove noise, analyze the code to retain useful inline notes that document implicit contracts, while stripping redundant boilerplate that simply restates what the code already shows.

Yes, you can document implicit contracts without boilerplate by analyzing code to add purposeful documentation only where non-obvious decisions exist, respecting the existing structure rather than overwriting it with redundant explanations.

Yes, this code clarity approach works during code reviews and maintenance by analyzing existing code to improve readability, identifying non-obvious logic, and removing noise while preserving useful comments already present.

You should avoid adding inline comments when the code is already obvious, as the goal is to remove noise and reduce cognitive load rather than generate boilerplate that simply restates what the code does.