pr-mine

Lists the current user's open GitHub PRs grouped by merge readiness with Slack ping messages.

Updated May 11, 2026
One-click install
npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill pr-mine-thachrocky12345
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-mine
Source: https://github.com/thachrocky12345/local-agent-train-workstation/tree/main/qvac/.cursor/skills/pr-mine
Command: npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill pr-mine-thachrocky12345

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Tracking your own open pull requests across multiple teams is tedious: you must check review status, figure out who still owes an approval, and manually chase reviewers. This Skill automates that by surfacing all your open PRs in tetherto/qvac, grouping them by merge readiness, and generating copy-paste Slack messages routed to the correct owning pod. ## Core Features & Use Cases - Cross-pod PR discovery: Auto-detects the owning pod for each PR by matching touched files against every .github/teams/<pod>.json ownedPaths, so no --pod argument is needed. - Merge-readiness grouping: Buckets PRs into ready to merge, needs re-review, awaiting review, and no pod matched, based on team member and team lead approvals. - Slack ping generation: Produces copy-paste-ready Slack messages with @-mentions resolved from a per-user handle map at ~/.config/qvac-pr-skills/slack.json, including a validation gate to confirm newly discovered handles. - Use Case: Before standup, run the skill to see which of your five open PRs are blocked, then paste the generated Slack messages to ping the right reviewers on each owning team. ## Quick Start Ask the assistant to show your open PRs and who to ping, or invoke /pr-mine directly.

Frequently Asked Questions about pr-mine

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

FAQPage Schema
How do I see all my open GitHub PRs and their review status?▼

Run the pr-status script with --mode my via the gh CLI. It lists your open PRs in tetherto/qvac grouped into ready to merge, needs re-review, awaiting review, and no pod matched, based on team member and lead approvals.

How do I generate Slack messages to ping PR reviewers?▼

The skill outputs copy-paste-ready Slack messages for PRs needing review, with @-mentions resolved from ~/.config/qvac-pr-skills/slack.json. If a handle is unmapped, it falls back to @<github-login> until you confirm or edit the mapping.

How does the skill know which team owns a pull request?▼

It lists each PR's touched files via the GitHub API and matches them against the ownedPaths prefixes in every .github/teams/<pod>.json file. The first matching pod in readdir order supplies the leads, members, and Slack handles for ping logic.

What happens when a PR touches files owned by multiple pods?▼

The first pod whose ownedPaths matches any touched file wins, and remaining pods are ignored. This suits single-team PRs; if two pods frequently share files, rename one pod directory so the preferred pod sorts first.

Why does the skill ask me to validate Slack handles on first run?▼

New logins discovered in team files are auto-seeded from the GitHub API into pendingReview in slack.json. The validation gate asks you to confirm or correct each proposed handle before output is shown, preventing wrong @-mentions.

What are the prerequisites for running this PR tracking skill?▼

You need the gh CLI installed and authenticated, access to the tetherto/qvac repository, at least one .github/teams/<pod>.json metadata file, and a per-user slack.json handle map, which is auto-bootstrapped on first run.