merge-fix-until-satisfied

Apply PR review fixes, commit changes, and re-check until satisfied.

Updated May 16, 2026
One-click install
npx skills add https://github.com/cedricfarinazzo/agile-skills --skill merge-fix-until-satisfied
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-fix-until-satisfied
Source: https://github.com/cedricfarinazzo/agile-skills/tree/main/agile-merge-review/skills/merge-fix-until-satisfied
Command: npx skills add https://github.com/cedricfarinazzo/agile-skills --skill merge-fix-until-satisfied

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fix every issue from a PR review by applying fixes, committing changes, re-checking, and repeating until satisfied.

Core Features & Use Cases

  • Phase-driven workflow: detect issues from PR reviews, apply fixes, commit with clear messages, and re-run the review until no issues remain.
  • Opportunistic cleanup: perform small, low-risk improvements during re-review to enhance code quality.
  • Ready-for-merge assurance: ensures downstream actions like merge can proceed only after satisfaction criteria are met.

Quick Start

Run merge-fix-until-satisfied after a merge-review-pr to auto-fix issues, commit changes, and re-check until the PR is ready to merge.

Frequently Asked Questions about merge-fix-until-satisfied

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

FAQPage Schema
How do I automatically fix issues found in a git pull request review?▼

To automatically fix pull request review issues, you can use a phase-driven workflow that applies fixes, commits changes, and re-checks until no issues remain. This handles iterative corrections across multiple files before merging.

What is PR review churn and how does iterative code review fix it?▼

PR review churn is the cycle of receiving feedback, applying fixes, and re-requesting review. Iterative code review automation resolves it by applying changes, committing with clear messages, and re-running checks until satisfaction criteria are met.

Can I automate code cleanup during an autonomous merge-review workflow?▼

Yes, you can perform opportunistic cleanup during an autonomous merge-review workflow. It executes small, low-risk improvements alongside required fixes to enhance code quality before the final merge gates are met.

How do I ensure a pull request is ready for merge after applying review feedback?▼

To ensure a pull request is ready for merge, run a re-check workflow that applies fixes and commits changes until the review is satisfied. This provides ready-for-merge assurance so downstream actions proceed only when gates pass.

What are the limitations of automating PR fixes across multiple files?▼

Automating PR fixes across multiple files operates strictly within phase-driven execution limits, stopping only when the review is satisfied or all gates are met. It cannot bypass satisfaction criteria or proceed with unresolved issues.