skills.rest
kanade0404
kanade0404COMMUNITY
Explore all skills by this author →
Website𝕏@py_kanade0404GitHub

pr-monitor

Monitor GitHub pull requests until merged or closed, then trigger the retro workflow.

Updated May 17, 2022
Search Tags:#automation#monitoring#pull request#github#polling#retro
One-click install
npx skills add https://github.com/kanade0404/dotfiles --skill pr-monitor-kanade0404
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-monitor
Source: https://github.com/kanade0404/dotfiles/tree/main/.opencode/skills/pr-monitor
Command: npx skills add https://github.com/kanade0404/dotfiles --skill pr-monitor-kanade0404

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps long-running pull requests under watch until they reach a final outcome, so you do not have to repeatedly check their status by hand.

Core Features & Use Cases

  • End-to-end PR state monitoring: Tracks a PR from open status through merge or close, then hands off to retro automatically.
  • Flexible waiting strategies: Chooses between scheduled polling, session wakeups, or manual re-check instructions depending on what the environment supports.
  • Durable state handling: Saves monitoring progress in a gitignored state file so later checks can resume without losing context.
  • Use case: After you ship a branch and create a PR, this Skill can keep observing it for hours or days until the final decision is made.

Quick Start

Ask me to monitor a specific pull request until it is merged or closed, and automatically continue into retro when it reaches a final state.

Frequently Asked Questions about pr-monitor

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

FAQPage Schema
How do I monitor a pull request until it is merged or closed?▼

This Skill tracks the pull request state using GitHub CLI until it reaches a final merged or closed state, then automatically triggers the retro workflow with the final outcome. It handles long-running PR lifecycle tracking so you do not check status manually.

Does this PR monitoring require the GitHub CLI to inspect state?▼

Yes, this PR monitoring requires the GitHub CLI to inspect pull request states. It relies on GitHub CLI commands to determine if a PR is merged or closed before saving monitoring progress in a durable gitignored state file and triggering the retro workflow.

How do I resume GitHub PR lifecycle tracking if my session drops?▼

You can resume GitHub PR lifecycle tracking because this Skill saves monitoring progress in a durable gitignored state file. Later checks or recurring re-entries resume from this saved state without losing context, ensuring continuous PR observation.

What is the best way to automate tracking long-running pull requests?▼

Automating long-running pull request tracking involves flexible waiting strategies like scheduled polling, session wakeups, or manual re-check instructions. This Skill keeps observing the PR for hours or days until the final merge or close decision is reached.

Can I track auto-detected branch PRs or do I need an explicit PR number?▼

You can track both auto-detected branch PRs and explicit PR numbers. This Skill applies to long-running GitHub PR lifecycle tracking by accepting explicit PR numbers, automatically detecting branch PRs, and supporting recurring check-only re-entry.

Related Skills

Explore More Software Engineering Skills→
garochee33garochee33
3

github

Manage GitHub repository operations including pull request triage, Actions monitoring, branch protection, and releases.

Community
Advanced
joshka0joshka0
3

foxctl CI

Retrieve GitHub pull request CI check outcomes and review comments.

Community
Basic
fredchufredchu
2

earnings-status

Monitor earnings call transcript processing statuses and cron job listings.

Community
Intermediate
chicago-joechicago-joe

babysit

Monitor GitHub pull request checks, reviews, and CI status for merge readiness.

Community
Intermediate