How do I install the Qv Sdk Pr Status skill?

Run npx skillmds@latest add tetherto/qv-sdk-pr-status in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Qv Sdk Pr Status safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Qv Sdk Pr Status?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Qv Sdk Pr Status free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Qv Sdk Pr Status?

tetherto (@tetherto) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Qv Sdk Pr Status by tetherto — Agent Skill

Name: Qv Sdk Pr Status
Author: tetherto

Qv Sdk Pr Status

Team-wide PR dashboard for the SDK pod. Shows open PRs touching SDK pod paths, SDK docs, or authored by SDK roster members, sorted oldest-first, grouped by author tier (SDK Core / Platform / External) into needs-your-re-review / stale / needs-review / fully-approved, with a Docs lane, per-platform e2e on Core impl PRs, merge-conflict and CI-red warnings. Use when checking team SDK pod PR status or invoking /qv-sdk-pr-status.

tetherto 003dfad 2 files · 2.5 KB Updated Sep 17, 2026

File contents

SDK Pod PR Status

Thin wrapper over the shared pr-skills library, pinned to the SDK pod. PR data collection lives in .agents/skills/_lib/pr-skills/pr-activity.mjs; this skill keeps the SDK-specific invocation. Docs-only PRs (docPaths in sdk.json) render in a Docs lane. SDK Core impl PRs include a per-platform e2e: line. approvalLeads in sdk.json count as lead approval without becoming Core authors.

When to use this skill

Use when:

User asks about open SDK pod PRs, review status, or what needs attention
User wants to know which SDK pod PRs to review
User invokes /qv-sdk-pr-status

Prerequisites

gh CLI installed and authenticated (gh auth status)
User must have access to the configured GitHub repository
Team roster maintained at .github/teams/sdk.json

Usage

node .agents/skills/_lib/pr-skills/pr-status.mjs --pod sdk --mode team --authors union --tiers

--authors union — PRs that touch SDK ownedPaths or docPaths, or are authored by an SDK roster member
--tiers — split into SDK Core / Platform/Middleware / External Contribution (opt-in; other pods stay flat unless they pass the flag)

For the personal review queue, use --mode review. The script and its output format are documented in .agents/skills/_lib/pr-skills/README.md.

Machine-readable output for daily status workflows:

node .agents/skills/_lib/pr-skills/pr-status.mjs --pod sdk --mode team --authors union --tiers --json

Workflow

Run the script with --pod sdk --mode team --authors union --tiers.
Present the script's markdown output as-is to the user (do not reformat into tables or fenced code blocks). Stderr contains progress info — ignore it.
Surface the summary header counts (core / platform / external / re-review / stale / fully approved / merge conflicts) prominently.
After showing results, offer: "Want me to review any of these? Provide the PR URL and I'll run /qv-pr-review."

---name: qv-sdk-pr-statusdescription: Team-wide PR dashboard for the SDK pod. Shows open PRs touching SDK pod paths, SDK docs, or authored by SDK roster members, sorted oldest-first, grouped by author tier (SDK Core / Platform / External) into needs-your-re-review / stale / needs-review / fully-approved, with a Docs lane, per-platform e2e on Core impl PRs, merge-conflict and CI-red warnings. Use when checking team SDK pod PR status or invoking /qv-sdk-pr-status.---# SDK Pod PR StatusThin wrapper over the shared pr-skills library, pinned to the SDK pod. PR data collection lives in `.agents/skills/_lib/pr-skills/pr-activity.mjs`; this skill keeps the SDK-specific invocation. Docs-only PRs (`docPaths` in sdk.json) render in a Docs lane. SDK Core impl PRs include a per-platform `e2e:` line. `approvalLeads` in sdk.json count as lead approval without becoming Core authors.## When to use this skill**Use when:**- User asks about open SDK pod PRs, review status, or what needs attention- User wants to know which SDK pod PRs to review- User invokes `/qv-sdk-pr-status`## Prerequisites- `gh` CLI installed and authenticated (`gh auth status`)- User must have access to the configured GitHub repository- Team roster maintained at [.github/teams/sdk.json](../../../.github/teams/sdk.json)## Usage```bashnode .agents/skills/_lib/pr-skills/pr-status.mjs --pod sdk --mode team --authors union --tiers```- `--authors union` — PRs that touch SDK `ownedPaths` or `docPaths`, **or** are authored by an SDK roster member- `--tiers` — split into SDK Core / Platform/Middleware / External Contribution (opt-in; other pods stay flat unless they pass the flag)For the personal review queue, use `--mode review`. The script and its output format are documented in [.agents/skills/_lib/pr-skills/README.md](../_lib/pr-skills/README.md).Machine-readable output for daily status workflows:```bashnode .agents/skills/_lib/pr-skills/pr-status.mjs --pod sdk --mode team --authors union --tiers --json```## Workflow1. Run the script with `--pod sdk --mode team --authors union --tiers`.2. Present the script's markdown output **as-is** to the user (do not reformat into tables or fenced code blocks). Stderr contains progress info — ignore it.3. Surface the summary header counts (core / platform / external / re-review / stale / fully approved / merge conflicts) prominently.4. After showing results, offer: "Want me to review any of these? Provide the PR URL and I'll run `/qv-pr-review`."

Frequently asked questions