sdk-pr-status

Display open SDK pull requests categorized by review needs, staleness, and conflicts.

395|94|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/tetherto/qvac --skill sdk-pr-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdk-pr-status
Source: https://github.com/tetherto/qvac/tree/main/.cursor/skills/sdk-pr-status
Command: npx skills add https://github.com/tetherto/qvac --skill sdk-pr-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a centralized dashboard for tracking the status of open pull requests related to the SDK pod, simplifying review workflows.

Core Features & Use Cases

  • PR Tracking: Displays open pull requests touching SDK paths, categorized by review status and conflicts.
  • Team Coordination: Helps teams identify PRs needing re-review, those that are stale, or with merge conflicts.
  • Use Case: When a developer or reviewer wants to quickly see which SDK PRs require attention or review, they run this Skill to get an organized overview.

Quick Start

Use the sdk-pr-status skill to check the current pull request status for your SDK team.

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 the status of open SDK pull requests on GitHub?

To check SDK pull request status, this Skill displays open GitHub PRs touching SDK paths, categorizing them by review needs, stale status, and merge conflicts to provide an organized team overview.

How do I identify stale pull requests in my SDK codebase?

You can identify stale pull requests by viewing the categorized dashboard, which highlights open SDK PRs that are stale, require re-review, or contain merge conflicts for efficient team coordination.

Can I track GitHub pull requests that have merge conflicts for my SDK team?

Yes, you can track GitHub PRs with merge conflicts because the Skill categorizes open SDK-related pull requests by their review status, staleness, and conflict state for team management.

What is the best way to manage code review workflows for an SDK pod?

The best way to manage SDK code review workflows is using a centralized dashboard that tracks open pull requests, helping teams quickly identify which SDK PRs require attention or review.

How do I find which SDK pull requests need re-review?

To find SDK PRs needing re-review, run this Skill to generate an organized overview that categorizes open pull requests based on their current code review status and team requirements.