pr-watch

Name: pr-watch
Availability: InStock
Author: shiroino

Monitor CI status, review threads, and implement patches for pull requests.

Updated Mar 28, 2026

Search Tags:#automation #workflow #merge #code-review #pull-request #ci-monitoring #pr-watch

Ready to run

npx skills add https://github.com/shiroinock/nv-atlas --skill pr-watch-shiroinock

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-watch
Source: https://github.com/shiroinock/nv-atlas/tree/main/.claude/skills/pr-watch
Command: npx skills add https://github.com/shiroinock/nv-atlas --skill pr-watch-shiroinock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR workflows often suffer from fragmented feedback loops: CI failures, review discussions, and patch integration can delay merges.

Core Features & Use Cases

Automates CI monitoring for a PR to surface failures and status at a glance.
Manages review threads by summarizing open discussions and proposing action items.
Orchestrates the PR lifecycle from detection to patch implementation to speed up merges.

Quick Start

Run /pr-watch 123 to monitor PR #123 and automatically track CI status and review activity.

Frequently Asked Questions about pr-watch

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

FAQPage Schema

How do I automate PR CI monitoring to speed up merges?▼

Automate PR CI monitoring to speed up merges by tracking CI status, detecting failures, and managing review threads. This reduces fragmented feedback loops across patch integration and code reviews.

What is the best way to track unresolved code review threads on a pull request?▼

Track unresolved code review threads by summarizing open discussions and proposing aligned action items. This manages review cycles by orchestrating patch implementation for collaborative development.

How do I monitor CI status for a specific pull request?▼

Monitor CI status for a specific pull request by running a targeted command with the PR number. This initiates tracking of CI activity and surfaces unresolved review threads automatically.

Can I automate patch implementation based on code review discussions?▼

You can automate patch implementation based on code review discussions through controlled rework cycles. This proposes aligned actions and orchestrates the PR lifecycle with autonomous decision-making.

Why do my pull request workflows suffer from delayed merges?▼

Pull request workflows suffer from delayed merges due to fragmented feedback loops where CI failures, review discussions, and patch integration cause bottlenecks. Automating this lifecycle speeds up mergers.

Are there limitations to autonomous decision-making in PR lifecycle orchestration?▼

Autonomous decision-making in PR lifecycle orchestration operates within controlled rework cycles. It proposes aligned actions for patch implementation but requires collaborative development to manage unresolved threads effectively.