writing-code-review-reports
Writing Code Review Reports
Turn existing review results into a report the reader can understand and act on without the reviewer's session. Preserve what the evidence says, what it does not establish, and what the author should do next. Useful reporting is not a second review or a more confident version of the first one.
Boundary and Reporting Mode
Use after results exist, whether supplied by others or produced by the agent in the current task,
including the reporting stage of a request to review and write a report. A requested report can be
short and delivered in chat; neither a separate file nor the word "handoff" is required.
Code inspection belongs to reviewing-code-changes; explanation-only walkthroughs belong to
understanding-code-changes. Neither skill is required to report from supplied results. A brief
findings-only review reply when no report is requested does not automatically need this skill,
a report file, or a full template.
Choose the mode from the request; ask only if the ambiguity would change the deliverable: