pr-review-fix

Analyze and resolve CI failures, review feedback, and merge conflicts across open GitHub pull requests.

1.1k|133|Updated May 23, 2025
One-click install
npx skills add https://github.com/TencentCloudBase/CloudBase-AI-Toolkit --skill pr-review-fix-tencentcloudbase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-fix
Source: https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/skills/pr-review-fix
Command: npx skills add https://github.com/TencentCloudBase/CloudBase-AI-Toolkit --skill pr-review-fix-tencentcloudbase

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the bottleneck of managing multiple open pull requests by automating the triage of CI failures, addressing review feedback, and resolving merge conflicts.

Core Features & Use Cases

  • Automated Triage: Systematically classifies PR health based on CI status, review decisions, and mergeability.
  • Batch Fixes: Executes local reproduction, applies fixes for common build/test errors, and pushes updates to PR branches.
  • Use Case: When a repository has dozens of stale PRs with failing tests or requested changes, this skill identifies the highest priority issues and applies the necessary code corrections to restore PR health.

Quick Start

Use the pr-review-fix skill to analyze all open pull requests and apply necessary fixes for any identified CI failures or review comments.

Frequently Asked Questions about pr-review-fix

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

FAQPage Schema
How do I automate fixing GitHub pull request CI failures and merge conflicts?

Automating GitHub pull request triage involves fetching PR metadata, reproducing build or test errors locally, and applying conventional-changelog compliant fixes to PR branches to restore repository health.

What is the best way to manage multiple open pull requests with stale code review feedback?

Managing stale pull requests requires systematically classifying PR health based on CI status, review decisions, and mergeability, then batch applying necessary code corrections to resolve requested changes.

Can I batch fix failing tests across multiple GitHub pull request branches?

Yes, you can batch fix failing tests by executing local reproduction of build errors across open GitHub pull requests and automatically pushing conventional-changelog compliant updates to the respective PR branches.

Does this automated code review fix process work without external dependencies?

Yes, this automated code review and CI fix process operates without external dependencies, directly fetching GitHub PR metadata and applying updates to branches to maintain pipeline health.

How do I monitor CI pipeline health for automated repository maintenance?

Monitoring CI pipeline health for automated repository maintenance involves systematically analyzing CI failures, review decisions, and mergeability across open GitHub pull requests to identify and resolve high priority issues.

What are the limitations of automated PR triage for resolving merge conflicts?

Automated PR triage resolves merge conflicts by applying conventional-changelog compliant fixes to branches, but limitations arise when complex reproduction errors require manual intervention beyond standard build or test failures.