skills.rest
OmniNode-ai
OmniNode-aiOFFICIAL
Explore all skills by this author →
GitHub

pr-polish

Resolve conflicts, address review comments, and fix CI failures for pull requests.

3|1|Updated Oct 9, 2025
Search Tags:#automation#git#ci/cd#code review#pull request#merge conflicts#pr
One-click install
npx skills add https://github.com/OmniNode-ai/omniclaude --skill pr-polish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-polish
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/pr-polish
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill pr-polish

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the entire process of getting a pull request ready to merge, from resolving merge conflicts to addressing all review comments and CI failures, ensuring a clean and deployable state.

Core Features & Use Cases

  • Conflict Resolution: Automatically detects and resolves merge conflicts against the base branch.
  • Review & CI Fixes: Fetches and addresses all review comments and CI failures using specialized sub-skills.
  • Iterative Local Review: Runs a loop of local code review until a specified number of clean passes are achieved.
  • Use Case: A developer opens a PR, but it has merge conflicts and a few CI errors. Running /pr-polish will automatically fix these issues, push the changes, and even arm GitHub's automerge feature if configured.

Quick Start

Use the pr-polish skill to prepare the current pull request for merging.

Frequently Asked Questions about pr-polish

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

FAQPage Schema
How do I automatically resolve merge conflicts in a pull request?▼

You can automatically resolve merge conflicts by running a multi-phase workflow that detects conflicts against the base branch and dispatches specialized agents to fix them. This process pushes the corrected changes to make the branch deployable.

What is the best way to address GitHub review comments and CI failures together?▼

Addressing GitHub review comments and CI failures together requires a workflow that fetches all feedback and dispatches specialized sub-skills to process the reviews and fix the errors. This ensures the codebase meets all quality checks before merging.

Can I use an automated workflow to fix pull request errors and arm GitHub automerge?▼

Yes, you can use an automated workflow to fix pull request errors and optionally arm GitHub automerge. It orchestrates conflict resolution, review processing, and CI fixes, arming automerge upon successful completion of all checks.

Does iterative local code review help get a pull request ready for merging?▼

Iterative local code review helps get a pull request ready for merging by running continuous code quality checks in a loop until a specified number of clean passes are achieved. This guarantees the code meets strict quality standards before pushing.

When do I need to run an automated pull request workflow instead of fixing CI errors manually?▼

You need to run an automated pull request workflow instead of fixing CI errors manually when a PR has multiple overlapping merge conflicts, review comments, and failing pipelines. Automating these fixes ensures a clean state without manual intervention.

Related Skills

Explore More Software Engineering Skills→
pegasus-isipegasus-isi

babysit-pr

Automate pull request lifecycle with GitHub CLI and git worktrees.

Official
Advanced
avvaleavvale

commit-pr

Commit changes, push to a feature branch, and create a GitHub Pull Request.

Official
Advanced
jimmymalhanjimmymalhan
1

pr-reviewers

Automate pull request reviews with specialized agents and enforce merge gates.

Community
Advanced
kaiohenricunhakaiohenricunha

review-pr

Automate GitHub pull request review, fix application, and validation workflows.

Community
Advanced