agentleFS
Sign inStart free
tethertotetherto/qvac/.agents/skills/qv-sdk-pr-status/SKILL.md

qv-sdk-pr-status

Skill697 starsChanged 18 days agoApache-2.0View on GitHub

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.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the script with --pod sdk --mode team --authors union --tiers.

    line 44
  2. Very specific:

    After showing results, offer: "Want me to review any of these?

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. 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."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free