dev-step--followup-pr

Identify CI failures, review comments, and merge conflicts in GitHub pull requests.

Updated Sep 27, 2020
One-click install
npx skills add https://github.com/tetetratra/dotfiles --skill dev-step-followup-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-step--followup-pr
Source: https://github.com/tetetratra/dotfiles/tree/main/claude/skills/dev-step--followup-pr
Command: npx skills add https://github.com/tetetratra/dotfiles --skill dev-step-followup-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR作成後に発生するCI失敗、レビューディアログ、コンフリクトといった問題を特定して、対応の優先順位をつける作業を自動化します。

Core Features & Use Cases

  • CIチェックの状態確認: 失敗しているジョブを特定し、関連ログを整理する。
  • レビュー指摘の整理と対応計画: 未解決コメントを抽出し、対応方針をリスト化する。
  • コンフリクト検出と解決案の提示: マージ可能性を評価し、必要に応じてリベースやマージの手順を提案する。
  • Use Case: 大規模チームの複数PRを同時に追跡し、優先度の高い対応をリードする。

Quick Start

Assess the current open PR and outline prioritized actions to resolve CI failures, review comments, and conflicts.

Frequently Asked Questions about dev-step--followup-pr

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

FAQPage Schema
How do I triage CI failures and review comments on a GitHub pull request?

You can triage GitHub pull requests by automatically fetching PR status to identify failed CI jobs, extracting unresolved review comments, and organizing prioritized remediation actions across multiple checks.

What is the best way to track and prioritize fixes for multiple PRs across different branches?

Tracking and prioritizing fixes for multiple PRs across different branches involves evaluating merge readiness, surfacing conflicts, and listing remediation steps to lead high-priority responses in large teams.

How do I detect merge conflicts and propose resolution steps for a pull request?

Detect merge conflicts by evaluating merge readiness, then surface conflicts and propose required resolution steps like rebase or merge procedures to ensure the pull request integrates cleanly.

Does this PR triage workflow work for large teams managing multiple open pull requests?

Yes, this PR triage workflow supports large teams managing multiple open pull requests simultaneously, organizing prioritized remediation actions across multiple reviewers, checks, and branches.

How do I organize unresolved review comments into an actionable resolution plan?

Organize unresolved review comments into an actionable resolution plan by extracting them from the PR dialog, listing response strategies, and prioritizing them alongside CI failures and merge conflicts.