fix-findings

Automating review findings fixes involves loading reviewer findings from an active session, parsing them by severity, and applying prioritized fixes automatically or with confirmation. This Skill handles the end-to-end workflow of loading, prioritizing, applying fixes, and updating the session resolution log.

Deduplicating reviewer findings across multiple reviewers involves loading findings from an active session, identifying duplicates, and generating a consolidated resolution report. This Skill automatically deduplicates findings across reviewers and tracks progress in a session resolution log.

Tracking progress when applying fixes to code review findings requires updating a session resolution log after each fix is applied. This Skill automatically updates the session resolution log after applying prioritized fixes, ensuring progress is tracked throughout the workflow.

Yes, you can apply code review fixes automatically without manual confirmation, or with confirmation if preferred. This Skill supports both automatic application and confirmation-based application of prioritized fixes from reviewer findings in an active review session.

Yes, you need a specific directory structure where reviewer findings are pasted into the active session directory, such as .chalk/reviews. This Skill reads findings from that directory, parses them by severity, applies fixes, and updates the resolution log.

Reviewer findings should be pasted as text into the active session directory for automated fix prioritization. This Skill reads the findings from the session directory, parses them by severity level, and applies prioritized fixes before updating the resolution log.