pr-fix

Fix CI failures, review comments, and merge conflicts to bring a GitHub PR to mergeable.

3|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/ronaknnathani/relay --skill pr-fix-ronaknnathani
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-fix
Source: https://github.com/ronaknnathani/relay/tree/main/skills/pr-fix
Command: npx skills add https://github.com/ronaknnathani/relay --skill pr-fix-ronaknnathani

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Open pull requests stall when CI checks fail, reviewers leave comments, or branches conflict with the base. This Skill drives a PR to a mergeable state by systematically diagnosing and fixing all three fronts instead of leaving authors to triage them manually. ## Core Features & Use Cases - CI failure diagnosis and repair: Reproduces failing checks locally, localizes the failing layer (type, import, config, dependency, environment), fixes the root cause, and adds a red-before/green-after regression test. - Review comment triage: Classifies each comment as non-actionable, an obvious gap-fix, or an author decision, then fixes, replies with a tracked agent marker, resolves threads via GraphQL, or flags decisions to the author. - Merge conflict resolution: Researches the intent behind both sides of each conflict using git log, blame, and PR history, resolves forward without aborting, and confirms the branch's commits survived. - Two operating modes: Runs a single pass over a watcher-supplied worklist in delegated mode, or loops its own assessment until the PR is clear in direct mode. - Use Case: After opening a PR, CI is red and a reviewer requested changes. Invoke this Skill to reproduce the failing test locally, fix the root cause, reply to each review thread with proper disclosure, resolve the base-branch conflict, and push until everything is green. ## Quick Start Ask the agent to bring the current pull request to a mergeable state by fixing CI failures, addressing review comments, and resolving merge conflicts.

Frequently Asked Questions about pr-fix

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

FAQPage Schema
How do I fix failing CI checks on a GitHub pull request?▼

Reproduce the failing check locally using the repository's own build or test command, localize the failing layer such as type, import, config, dependency, or environment, then fix the root cause. Add a regression test that fails without the fix and passes with it, and never skip or delete tests to go green.

How to resolve review comment threads on GitHub with the gh CLI?▼

Reply to inline comments via the pulls comments replies endpoint, then resolve the thread with the GraphQL resolveReviewThread mutation since gh has no native thread-resolve command. Only resolve a thread after the fix is actually pushed.

Can this Skill run automatically after a PR watcher event?▼

Yes, delegated mode accepts a worklist from relay pr watch containing items with reason, source, id, and answers tokens. It fixes each item once and returns a structured per-item result without re-running a broad assessment or touching the watcher record.

How should merge conflicts be resolved without losing changes?▼

Rebase or merge onto the base and research the intent behind both sides using git log, git blame, and the originating PRs before resolving. Never abort the rebase, re-run validation afterward, and confirm your commits still appear in git log with the intended net diff.

When should a review comment be flagged instead of fixed?▼

Flag a comment as an author decision when it changes intended behavior, API shape, or scope, or when two or more reasonable answers exist. Reply asking for input and leave the thread open rather than guessing the author's intent.