dxwatchpr

Monitor GitHub pull requests for CI failures and unresolved review feedback.

3|2|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/mitchellfyi/dex --skill dxwatchpr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dxwatchpr
Source: https://github.com/mitchellfyi/dex/tree/main/skills/dxwatchpr
Command: npx skills add https://github.com/mitchellfyi/dex --skill dxwatchpr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually tracking PR CI status, review feedback, and follow-up fixes consumes valuable engineering time and creates bottlenecks in the merge workflow, especially for teams with high PR volume.

Core Features & Use Cases

  • Automated CI Monitoring & Fixes: Continuously checks PR CI status, diagnoses common failures (lint, type errors, test failures, code generation drift), and pushes fixes without manual intervention for in-scope issues.
  • Review Feedback Management: Automatically addresses review comments, replies inline, resolves closed threads, and re-requests reviewers after new pushes to keep the review process moving.
  • Use Case: For software teams using GitHub, this skill eliminates the need to manually watch PRs after opening them – it handles routine fixes and only escalates issues requiring human architectural or scope decisions.

Quick Start

Use the dxwatchpr skill to monitor your open PR for CI failures and review feedback, automatically resolve routine issues, and alert you only if human intervention is needed.

Frequently Asked Questions about dxwatchpr

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

FAQPage Schema
How do I automate fixes for GitHub PR CI failures and review feedback?

Automating GitHub PR CI fixes and review feedback requires a watcher tool that monitors open pull requests, diagnoses common failures like lint or type errors, pushes fixes, and replies to comments automatically. This skill handles those routine tasks and escalates architectural or ambiguous issues to you.

What does automated PR monitoring do when CI checks fail?

Automated PR monitoring diagnoses continuous integration failures and attempts to push fixes for in-scope issues like code generation drift, type errors, and lint failures. It escalates secrets scan failures and architectural changes requiring human intervention instead of failing silently.

How do I automatically re-request reviewers after pushing fixes to a pull request?

Automatically re-requesting reviewers after pushing fixes requires a workflow automation skill that replies inline to review comments, resolves closed threads, and triggers reviewer notifications after new pushes. This keeps the review process moving without manual follow-up.

Do I need the GitHub CLI to monitor pull requests for CI issues?

Yes, you need the GitHub CLI installed and configured to monitor pull requests for CI issues and review feedback. The watcher relies on it to access repository data, push automated fixes, and interact with review threads.

What types of CI failures cannot be auto-resolved by a PR watcher?

A PR watcher cannot auto-resolve secrets scan failures, architectural changes, or ambiguous human feedback. These issues are escalated to the user because they require manual scope decisions and security verification beyond automated fixes.