apply-findings

Automates correction of assigned code findings module by module with validation before application.

5|3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/leifericf/agentic-sdk --skill apply-findings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apply-findings
Source: https://github.com/leifericf/agentic-sdk/tree/main/skills/apply-findings
Command: npx skills add https://github.com/leifericf/agentic-sdk --skill apply-findings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of applying findings to a module's code in a systematic and error-free manner, reducing manual effort and ensuring the integrity of the codebase.

Core Features & Use Cases

  • Simplified Code Correction: Automates the fixing of punch-list items assigned to a user, ensuring minimal disruption and correctness in one edit per item.
  • Confirmation Process: Prompts for code review and reproducibility before making any changes, enhancing code quality.
  • Scope Boundary: Enforces staying within the module and test namespace for code changes, preventing unnecessary cross-module edits.

Quick Start

Run the 'apply-findings' Skill to automatically apply corrections to the findings listed in your current code review.

Frequently Asked Questions about apply-findings

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

FAQPage Schema
How do I apply code review findings to a specific module without breaking other components?

To apply code findings safely, this Skill isolates changes to the specific module and test namespace in focus. It validates modifications before application to ensure minimal impact on other system components.

Can I automate fixing punch-list items assigned to a developer one by one?

Yes, you can automate fixing punch-list items. The process corrects one item per edit for a single module, prompting for reproducibility confirmation beforehand to maintain codebase integrity.

What is the best way to enforce module boundary enforcement during code correction?

Enforcing module boundaries during code correction requires restricting edits to the module and test namespace in focus. This Skill prevents unnecessary cross-module edits to maintain system integrity.

Does applying findings require reproducibility confirmation before making changes?

Yes, applying findings requires reproducibility confirmation. The Skill prompts for code review and reproducibility validation before making any changes to ensure correctness and minimal disruption.

Why should I isolate code changes to one module and one level at a time?

Isolating code changes to one module and one level at a time minimizes disruption. Validating changes before application ensures minimal impact on other system components and maintains codebase integrity.