vv-watch-pr

Monitor PR and CI status while diagnosing failures from GitHub Checks.

3|Updated Oct 16, 2025

Search Tags:#debug #cleanup #pr #flakes #ci #watch

Ready to run

npx skills add https://github.com/jdutton/vibe-validate --skill vv-watch-pr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vv-watch-pr
Source: https://github.com/jdutton/vibe-validate/tree/main/docs/skills/vv-watch-pr
Command: npx skills add https://github.com/jdutton/vibe-validate --skill vv-watch-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monitoring PR/CI status after pushes can be noisy and slow to diagnose; teams waste time sifting through raw logs. This Skill provides a focused view of CI status while surfacing extracted actionable state when vibe-validate data is available.

Core Features & Use Cases

Auto-detect the PR for the current branch and stream status updates from GitHub Checks.
Extract vibe-validate state YAML from CI notes when available to show the exact failing step, file, and message.
Detect flakes and surface reruns without new pushes, and support post-merge cleanup of local branches.
Use cases: debugging flaky tests, triaging failing checks, tidying up branches after merges.

Quick Start

Run vv watch-pr to monitor the current branch's PR and stream CI status to your terminal.

Frequently Asked Questions about vv-watch-pr

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

FAQPage Schema

How do I monitor PR and CI status after pushing commits?▼

Diagnose CI failures by extracting vibe-validate state YAML from CI notes, which surfaces the exact failing step alongside precise file:line:message data for targeted debugging.

Can I detect flaky tests and CI reruns without creating new pushes?▼

Yes, you can detect flakes and surface CI reruns without new pushes. The tool actively monitors PR status transitions to identify intermittent flaky tests during continuous integration runs.

How do I cleanup local branches after a PR merge?▼

To cleanup local branches after a PR merge, use the post-merge cleanup feature. It automatically detects merged branches and helps tidy up your local repository environment.

What is the best way to triage failing GitHub Checks without reading raw logs?▼

The best way to triage failing GitHub Checks is using this tool to surface extracted actionable state. It filters noisy raw logs and highlights the specific failing step and validation messages.