fix-review

Interpret review feedback, plan minimal code fixes, and verify with tests and linting.

1|16|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/konflux-ci/.fullsend --skill fix-review-konflux-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-review
Source: https://github.com/konflux-ci/.fullsend/tree/main/skills/fix-review
Command: npx skills add https://github.com/konflux-ci/.fullsend --skill fix-review-konflux-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill simplifies the process of addressing review feedback on pull requests by automating the collection, planning, and fixing of code issues, reducing manual effort and ensuring consistency.

Core Features & Use Cases

  • Review Feedback Processing: Reads and interprets review comments, whether from bot-generated summaries or human instructions.
  • Automated Fix Planning: Determines minimal and effective code changes based on review feedback and code context.
  • Verification & Testing: Runs secret scans, linters, and tests to validate fixes before finalizing changes.
  • Use Case: Accelerate the review cycle by automatically applying suggested fixes, verifying code quality, and preparing well-documented commits for review.

Quick Start

Provide instructions to read review comments, plan fixes accordingly, and verify changes in a pull request.

Frequently Asked Questions about fix-review

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

FAQPage Schema
How do I automate code review fixes for pull requests?

Automating code review fixes involves interpreting review comments, planning minimal code changes, and verifying modifications with linting and tests. This process streamlines pull request workflows by automatically applying suggested fixes and preparing structured commits.

How does automated pull request feedback processing work?

Automated feedback processing reads and interprets review comments from bot-generated summaries or human instructions. It determines the necessary code modifications based on the review feedback and existing code context to plan minimal and effective fixes.

Can I use continuous integration testing to verify automated code fixes?

Yes, continuous integration testing is used to validate automated code fixes before finalizing changes. The process runs secret scans, linters, and automated tests to ensure secure and high-quality code modifications are committed.

What is the best way to plan minimal code changes from review comments?

Planning minimal code changes requires analyzing review feedback against the current code context. The automated fix planning approach determines the smallest effective modifications needed to resolve the issues identified in the pull request.

Does automated code fixing handle both bot and human review feedback?

Yes, automated code fixing handles both bot-generated summaries and human instructions. It collects and interprets review feedback from various sources to ensure consistent application of suggested fixes and code quality verification.

When should I not use automated code fixing for pull requests?

Automated code fixing may not be suitable for complex architectural changes requiring deep contextual understanding. It is designed for minimal, effective modifications and verifying code quality through secret scans, linters, and tests rather than extensive refactoring.