sdk-pr-status

Displays open SDK pod pull requests grouped by review status with merge-conflict warnings.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It gives SDK pod team members a single dashboard view of open pull requests touching SDK pod paths, so they can quickly see which PRs need re-review, which are stale, and which have merge conflicts. ## Core Features & Use Cases - Team PR Dashboard: Lists open PRs touching SDK pod paths, sorted oldest-first and grouped into needs-your-re-review, stale, and needs-review buckets. - Merge-Conflict Warnings: Surfaces PRs with merge conflicts so they can be addressed before review. - Personal Review Queue: Supports a --mode review flag for an individual review queue instead of the team view. - Use Case: A developer starts their day by running the skill to see which SDK pod PRs are waiting on their re-review and which have gone stale, then picks one to review with /pr-review. ## Quick Start Ask the assistant to show the current SDK pod PR status, or invoke /sdk-pr-status to run the dashboard.

Frequently Asked Questions about sdk-pr-status

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

FAQPage Schema
How do I check open PRs for the SDK pod team?

Run the pr-status script with --pod sdk --mode team, or invoke /sdk-pr-status. It lists open PRs touching SDK pod paths, sorted oldest-first and grouped by review status.

How do I see only my personal PR review queue on GitHub?

Use the same script with --mode review instead of --mode team. This switches the output from the team-wide dashboard to your personal review queue.

What are the prerequisites for running the SDK PR status script?

You need the gh CLI installed and authenticated (verify with gh auth status), access to the tetherto/qvac repository, and a team roster maintained at .github/teams/sdk.json.

Does the SDK PR status dashboard detect merge conflicts?

Yes, the dashboard includes merge-conflict warnings alongside the grouped PR lists, and the summary header surfaces counts for re-review, stale, and conflicted PRs.

Why does the SDK PR status script fail with authentication errors?

Failures usually mean the gh CLI is not authenticated or lacks access to tetherto/qvac. Run gh auth status to verify your session and confirm repository permissions.