fix-findings

Apply prioritized fixes to codebase findings and update the resolution log.

6|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/GeneralJerel/chalk-skills --skill fix-findings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-findings
Source: https://github.com/GeneralJerel/chalk-skills/tree/main/skills/fix-findings
Command: npx skills add https://github.com/GeneralJerel/chalk-skills --skill fix-findings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read findings from the active review session and apply fixes to the codebase, then update the resolution log.

Core Features & Use Cases

  • Load findings from the active session and prioritize by severity
  • Apply fixes via a guided editing workflow and update the resolution log
  • Support deduplication across reviewers and audit trails

Quick Start

Paste reviewer findings into the active session and run the fix-findings workflow to apply prioritized fixes.

Frequently Asked Questions about fix-findings

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate fixes for code review findings in my codebase?

Automating fixes for code review findings involves loading active session findings, deduplicating similar issues across reviewers, prioritizing by severity, and applying changes through a guided workflow that updates the resolution log.

Can I deduplicate similar code review issues across multiple reviewers before applying fixes?

Yes, you can deduplicate similar code review issues across multiple reviewers. The workflow loads findings from the active session, groups overlapping issues, and prioritizes them by severity before guiding you through the resolution process.

How do I ensure safe updates when applying fixes to a codebase?

To ensure safe updates when applying codebase fixes, the workflow enforces strict path validation, reads surrounding file context for accuracy, and requires explicit user confirmation before applying any modification to the codebase.

What is the process for maintaining an auditable resolution log for codebase fixes?

Maintaining an auditable resolution log requires applying prioritized fixes to the codebase through a guided editing workflow, which automatically records each approved change and deduplicated issue into the active resolution log.

Does applying review findings require manual confirmation for every codebase change?

Yes, applying review findings requires manual confirmation for every codebase change. The workflow reads surrounding file context, enforces path validation, and prompts the user to approve each specific fix before writing it to the codebase.

What's the best way to prioritize codebase fixes from an active review session?

The best way to prioritize codebase fixes from an active review session is to load the findings, deduplicate overlapping issues across reviewers, sort them by severity, and process each change through a guided, auditable editing workflow.