skills.rest
hirokimry
hirokimryCOMMUNITY
Explore all skills by this author →
Website𝕏@hirokimryGitHub

pr-fix

Resolve GitHub pull request review comments and CI failures in one pass.

1|Updated Mar 20, 2026
Search Tags:#code review#pull request#github#coderabbit#graphql#worktree#ci
One-click install
npx skills add https://github.com/hirokimry/vibecorp --skill pr-fix-hirokimry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-fix
Source: https://github.com/hirokimry/vibecorp/tree/main/skills/pr-fix
Command: npx skills add https://github.com/hirokimry/vibecorp --skill pr-fix-hirokimry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR の未解決コメントや CI 失敗を、手作業で追いかけずに 1 回で修正して push できるようにします。レビュー対応の取りこぼしを減らし、単発の修正作業を素早く完了させます。

Core Features & Use Cases

  • 未解決コメントの修正: Open な PR のレビュー指摘を確認し、必要な修正だけを行います。
  • CI 失敗への対応: 失敗したチェックやログを見て、コード側で直せる問題をまとめて解消します。
  • 安全なレビュー運用: CodeRabbit の状態、Issue 側の intent ラベル、severity のフォールバックを踏まえて、修正対象と却下対象を分けて扱います。
  • Use Case: PR に細かい指摘が数件残っていて、まずは今の状態を確認してから修正を 1 回だけ適用し、そのまま push したいときに使います。

Quick Start

現在の PR の未解決コメントを確認して、必要な修正を 1 回だけ適用し、push まで実行してください。

Frequently Asked Questions about pr-fix

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

FAQPage Schema
How do I fix unresolved GitHub pull request comments and CI failures in one pass?▼

To fix unresolved GitHub pull request comments and CI failures in one pass, use a tool that detects open PR branches, fetches review threads via GraphQL, applies severity-based fallback logic, and executes a safe push-only workflow.

What is the best way to automate CodeRabbit review remediation for open pull requests?▼

Automating CodeRabbit review remediation for open pull requests requires parsing CodeRabbit review states alongside issue-label intent resolution to separate actionable fixes from dismissed items before applying code changes.

Does resolving GitHub PR review comments require GitHub CLI access?▼

Yes, resolving GitHub PR review comments through automated branch-based auto-detection requires GitHub CLI access to query review threads and push the remediated code changes safely back to the repository.

How do I handle CI failures and unresolved review threads using a worktree workflow?▼

Handling CI failures and unresolved review threads using a worktree workflow involves isolating the PR branch, fetching failed check logs and unresolved comments, applying fixes, and pushing once from the worktree.

When should I not use automated PR comment resolution?▼

You should not use automated PR comment resolution when review feedback requires architectural changes or discussion, as the severity-based fallback logic targets isolated code-level fixes suitable for single-pass remediation.

Can I use GraphQL pagination to fetch all unresolved PR review comments?▼

Yes, you can use GraphQL pagination to fetch all unresolved PR review comments by iterating through review threads on open pull requests to identify which actionable comments remain before applying fixes.

Related Skills

Explore More Software Engineering Skills→
haryelramalhoharyelramalho

gh-address-comments

Aggregate GitHub pull request review comments and threads via GraphQL.

Community
Intermediate
matt-rileymatt-riley
1

review-comment-resolution

Classify PR review comments and apply validated fixes to code branches.

Community
Intermediate
rito528rito528
1

issue-triage

Parse GitHub issue content and apply status labels via the GitHub API.

Community
Intermediate
alistairsteadalistairstead

gh-pr-comments

List unresolved GitHub PR review comments and resolve threads by thread_id.

Community
Advanced