pr-watch

Monitor GitHub PR CI status and apply targeted fixes from failure logs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mferris77/SpringBoard --skill pr-watch-mferris77
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-watch
Source: https://github.com/mferris77/SpringBoard/tree/main/vscode-citadel-harness/skills/pr-watch
Command: npx skills add https://github.com/mferris77/SpringBoard --skill pr-watch-mferris77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monitoring and fixing CI issues on pull requests from a local development environment to reduce context switching and manual re-checks.

Core Features & Use Cases

  • Monitors CI status for the current PR branch and reports updates in real-time.
  • Reads failure logs to identify actionable fixes and applies minimal changes, pushing a fix commit.
  • Optionally merges the PR when all checks pass, with safeguards and user confirmation.
  • Provides a CLI-like workflow that mirrors cloud auto-fix tools for offline/local use.

Quick Start

Run /pr-watch to start watching the current branch's PR checks and automatically apply fixes when failures occur.

Frequently Asked Questions about pr-watch

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

FAQPage Schema
How do I monitor GitHub PR CI status locally and automatically fix failures?▼

You can monitor GitHub PR CI status locally by running a CLI workflow that watches the current branch, reads failure logs, applies targeted fixes, and pushes a fix commit. It then re-checks CI to verify resolution.

How does local CI auto-fix workflow handle merging when checks pass?▼

The local CI auto-fix workflow optionally merges the PR when all GitHub checks pass. It includes safeguards and requires user confirmation before executing the merge to ensure branch stability.

What is the best way to apply minimal fixes to CI failures from my local repository?▼

The best way to apply minimal fixes to CI failures is using a deterministic local CLI workflow that reads failure logs, creates targeted fix commits, and triggers CI reruns without requiring context switching to cloud tools.

Can I automatically push fix commits for failing GitHub PR checks from my local environment?▼

Yes, you can automatically push fix commits for failing GitHub PR checks from your local environment. The workflow reads failure logs, generates a targeted patch, and pushes the commit to re-trigger CI.

Do I need cloud auto-fix tools to debug CI failures and merge GitHub PRs?▼

No, you do not need cloud auto-fix tools to debug CI failures. This local CLI workflow mirrors cloud auto-fix capabilities by orchestrating log reading, commit creation, and CI reruns entirely offline for your GitHub PRs.

Why does my local PR watch workflow require user confirmation before merging?▼

Your local PR watch workflow requires user confirmation before merging to act as a safeguard. This ensures a human verifies that all CI checks are green before the branch is merged into the repository.