mine.address-pr-issues

Triage and resolve PR blockers across GitHub and Azure DevOps.

8|1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Olatisunkanmi/claudefiles --skill mine-address-pr-issues-olatisunkanmi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mine.address-pr-issues
Source: https://github.com/Olatisunkanmi/claudefiles/tree/main/skills/mine.address-pr-issues
Command: npx skills add https://github.com/Olatisunkanmi/claudefiles --skill mine-address-pr-issues-olatisunkanmi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill addresses the challenge of triaging and resolving PR blockers like unresolved review comments, merge conflicts, and failing CI checks across GitHub and Azure DevOps.

Core Features & Use Cases

  • Platform detection from git remotes
  • Fetch PR metadata and review threads
  • Phase-based triage and targeted fixes with safety checks
  • Automated planning and execution of fixes with maintainers' review

Quick Start

Run the mine.address-pr-issues command with a PR number to start triaging and resolving blockers.

Frequently Asked Questions about mine.address-pr-issues

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

FAQPage Schema
How do I resolve unresolved PR review comments and merge conflicts?

To resolve PR review comments and merge conflicts, triage blockers by fetching PR metadata and review threads to build a phase-based plan that applies targeted fixes with explicit user confirmation before resolving threads.

How do I triage failing CI checks on a GitHub or Azure DevOps pull request?

Triage failing CI checks by automatically detecting your platform from the git remote, fetching the PR metadata, and applying phase-based fixes to resolve build blockers across GitHub and Azure DevOps.

Can I use automated PR triage across cross-repo scenarios in Azure DevOps and GitHub?

Yes, automated PR triage handles cross-repo scenarios across Azure DevOps and GitHub by detecting the platform from git remotes, fetching review threads, and enforcing safe thread-resolution procedures.

How do I start triaging a specific pull request blocker?

Start triaging a pull request blocker by running the triage command with the PR number, which fetches metadata and review threads to generate a phase-based resolution plan.

Does automated PR conflict resolution require explicit user confirmation before resolving threads?

Yes, automated PR conflict resolution requires explicit user confirmation before resolving threads, enforcing safe procedures and maintaining maintainer review during phase-based fix execution.