Verified:GitHub

kramme:iterate-pr

Automate PR iteration cycles to fix CI failures on GitHub and GitLab.

2|2|Updated Jan 15, 2026

Search Tags:#automation #workflow #GitHub #GitLab #CI #pull-request #iterate

One-click install

npx skills add https://github.com/Abildtoft/kramme-cc-workflow --skill kramme-iterate-pr

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: kramme:iterate-pr
Source: https://github.com/Abildtoft/kramme-cc-workflow/tree/main/skills/kramme%3Aiterate-pr
Command: npx skills add https://github.com/Abildtoft/kramme-cc-workflow --skill kramme-iterate-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the repetitive cycle of fixing CI failures on a pull request by orchestrating feedback collection, patch commits, and waiting for CI to re-run until all checks pass.

Core Features & Use Cases

Platform-agnostic workflow: Detects whether you are on GitHub or GitLab and uses the appropriate CLI to operate.
End-to-end PR iteration: Identifies the current pull request, checks CI status, gathers review feedback, and drives a fix-and-push loop until checks succeed.
Use Case: Imagine a PR with intermittent CI failures; this Skill guides you through making minimal fixes, pushing them with clear messaging, and waiting for green status automatically.

Quick Start

Trigger the skill on a branch with failing CI to begin an automated iterate-cycle. For example:

Run: /kramme:iterate-pr on the feature branch and follow any prompts.
Monitor CI status updates as the tool applies fixes and pushes commits.

Frequently Asked Questions about kramme:iterate-pr

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

FAQPage Schema

How do I automate fixing CI failures on a pull request?▼

Automating CI failure fixes involves orchestrating feedback collection, patch commits, and CI re-runs. This Skill drives an automated fix-and-push loop on your pull request, applying minimal fixes and pushing commits until all checks pass.

Does this PR iteration workflow support both GitHub and GitLab?▼

Yes, the PR iteration workflow is platform-agnostic and supports both GitHub and GitLab. It detects your current platform automatically and uses the appropriate CLI, either GitHub CLI or GitLab CLI, to execute the fix-and-push loop.

Do I need the GitHub CLI or GitLab CLI installed to automate pull request checks?▼

Yes, you need the GitHub CLI (gh) or GitLab CLI (glab) installed and authenticated. The Skill relies on these CLI tools being present in your environment to execute the commands required for checking CI status and pushing commits.

What is the process for iterating a pull request until CI passes?▼

The iteration process identifies your current pull request, checks the CI status, and gathers review feedback. It then guides you through making minimal fixes, committing patches with clear messaging, and waiting for CI to re-run automatically until checks succeed.

Can I trigger automated PR iteration on a branch with intermittent CI failures?▼

Yes, you can trigger the Skill on a feature branch with intermittent CI failures to begin the automated iterate-cycle. It monitors CI status updates, applies necessary fixes, and pushes commits automatically to drive the branch towards a green status.

When should I not use an automated fix-and-push loop for pull requests?▼

You should avoid using an automated fix-and-push loop when CI failures stem from complex architectural issues or missing dependencies, as the tool targets minimal fixes and clear messaging for intermittent failures rather than deep codebase refactoring.