Capture Review Findings

To persist code review findings to disk, you can capture and save them in a structured, triaged format. This ensures identified issues are not lost during context compaction and remain available for resolution in a fresh session.

You can triage code review findings by categorizing them into FIX, TASK, ADR, and RULE groups. This structured classification ensures clear actionability and helps track specific resolution paths for each identified issue.

Code review findings get lost during context compaction because session limits drop historical conversation data. Saving these findings to disk as structured files prevents this data loss and preserves the review outcomes for later access.

Yes, you can cross-reference code review findings with planning artifacts. The skill supports cross-referencing with documents like Spec.md and Steps.md to maintain alignment between identified issues and your project planning workflow.

The best way to save code review outcomes is writing detailed review files to a designated disk directory. This approach stores the triaged findings persistently, allowing you to address the documented issues systematically in a new session.

Yes, this code review workflow integration supports manual feedback. It is designed to be used after various review agents or manual feedback processes to capture, categorize, and save all identified issues to a file.