sdk-pr-create

Generate pull request descriptions from branch and commit data for SDK changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed PR titles and descriptions for SDK pod packages, reducing manual effort and ensuring consistency.

Core Features & Use Cases

  • Automated PR Drafting: Generates well-structured titles and bodies based on branch, commits, and change analysis.
  • Workflow Assistance: Guides users through inference of tickets, prefixes, and tags, minimizing manual input.
  • Use Case: When updating or releasing an SDK, the user can invoke this Skill to prepare accurate PR notes aligned with team standards, streamlining review processes.

Quick Start

Provide the command to generate a PR description for the current changes and open a PR using the output template.

Frequently Asked Questions about sdk-pr-create

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

FAQPage Schema
How do I automatically generate pull request descriptions for SDK packages?

Automatically generate pull request descriptions for SDK packages by parsing branch information and commit messages to produce standardized, high-quality PR summaries with minimal manual input. This ensures adherence to team formatting rules and streamlines the review process.

Does this PR automation tool work with the GitHub CLI?

Yes, this PR automation tool supports integration with GitHub CLI. You can invoke the skill to prepare accurate PR notes aligned with team standards and use the output template to open a PR directly through the GitHub CLI.

What is the best way to standardize PR titles and bodies for SDK feature branches?

The best way to standardize PR titles and bodies for SDK feature branches is using automated drafting tools that infer tickets, prefixes, and tags from commit data. This generates well-structured summaries aligned with team standards, minimizing manual input.

Can I infer ticket numbers and prefixes from commit messages when creating a PR?

Yes, you can infer ticket numbers and prefixes from commit messages when creating a PR. The workflow assistance feature guides users through the inference of tickets, prefixes, and tags, reducing manual effort and ensuring consistent formatting.

How to prepare accurate PR notes for an SDK release without manual formatting?

Prepare accurate PR notes for an SDK release without manual formatting by invoking an automated generation skill. It analyzes your current changes and branch data to output standardized descriptions, streamlining the release workflow and review processes.