pr-autofix

Ingest PR feedback and CI results to produce a merge-ready patch.

2|Updated Apr 11, 2025
One-click install
npx skills add https://github.com/abhimehro/personal-config --skill pr-autofix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-autofix
Source: https://github.com/abhimehro/personal-config/tree/main/.cursor/skills/pr-autofix
Command: npx skills add https://github.com/abhimehro/personal-config --skill pr-autofix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ingests PR review feedback and CI results and converts them into a single, merge-ready patch on the existing PR branch, reducing review storms and manual rework.

Core Features & Use Cases

  • Ingests review comments and CI results
  • Proposes and implements fixes
  • Pushes updates to the existing PR branch
  • Reports back with a structured, auditable summary (ELIR-aligned)

Quick Start

Ingest PR feedback and CI signals, plan a minimal secure fix, implement it on the existing PR branch, and push a single summary commit.

Frequently Asked Questions about pr-autofix

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

FAQPage Schema
How do I automatically fix PR review comments and CI failures?

To automatically fix PR review comments and CI failures, this Skill ingests feedback and CI results to produce a single, merge-ready patch on the existing branch. It handles the entire process through ingest, plan, implement, verify, and report stages.

Can I automate code review fixes on my existing PR branch without leaking secrets?

Yes, you can automate code review fixes without leaking secrets. The process applies strict guardrails to avoid secret leakage, destructive actions, and unvetted dependencies while implementing fixes on your existing PR branch.

How does automated PR fixing handle commit messages and reporting?

Automated PR fixing handles commit messages and reporting by generating auditable commit messages and a concise ELIR-aligned report. This structured summary ensures full traceability of the automated changes pushed to the branch.

What is the best way to turn CI feedback into a merge-ready patch?

The best way to turn CI feedback into a merge-ready patch is ingesting CI signals and review comments to propose, implement, and verify a minimal secure fix. It pushes updates as a single summary commit to reduce manual rework.

Are there limitations to automating PR fixes for multiple repositories?

Yes, a limitation is that the automation handles one PR at a time and applies specifically to personal-config, email-security-pipeline, and ctrld-sync PRs. It requires strict guardrails to prevent unvetted dependencies and destructive actions.

Do I need to set up special dependencies to automate code review fixes?

No special dependencies are required to automate code review fixes. The Skill operates independently to ingest feedback, plan a minimal secure fix, and push updates directly to the existing PR branch.