sdk-pr-create

Generate PR titles and descriptions for SDK pod packages following team templates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-formatted pull request descriptions for SDK pod packages is repetitive and error-prone, especially when titles must follow strict ticket/prefix/tag conventions and release branches require a follow-up backmerge PR. ## Core Features & Use Cases - Automated PR Generation: Infers ticket number, prefix (feat/fix/doc), and tags ([api]/[bc]/[mod]) from branch names, commits, and diffs, then fills the team PR template. - gh CLI Integration: Creates the PR directly via the GitHub CLI with correct fork/upstream handling, or outputs copy-ready markdown when gh is unavailable. - Release Dual-PR Flow: When targeting a release branch, automatically chains into the sdk-backmerge skill to open a second PR against main. - Use Case: You finish a feature on branch feat/QVAC-1234-new-api targeting release-core-1.2.0. Invoke the skill to generate a compliant PR title and body, create the release PR with gh, and automatically open the backmerge PR to main. ## Quick Start Ask the assistant to create a PR for the current SDK pod branch using the sdk-pr-create skill.

Frequently Asked Questions about sdk-pr-create

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

FAQPage Schema
How do I generate a PR description for an SDK pod package?

Invoke the sdk-pr-create skill on your feature branch. It collects commits and diffs against the base branch, infers the ticket, prefix, and tags, then fills the team PR template and outputs a copy-ready title and body.

How do I create a GitHub PR from a fork using the gh CLI?

Use gh pr create with explicit --repo, --base, and --head flags, where --head is FORK_OWNER:BRANCH. The skill checks for gh, verifies remotes, and runs this command after your changes are committed and pushed.

When are the [api], [bc], and [mod] tags required in a PR title?

Use [api] when adding new exported functions or types, [bc] when changing or removing existing public API signatures, and [mod] when modifying model constant definitions. The skill infers these from the diff and asks only when the scope is ambiguous.

What happens when the PR targets a release branch?

The skill automatically chains into the sdk-backmerge workflow to open a second PR against main with the same version-bump and changelog metadata. You can skip this with the --no-backmerge flag.

What if the backmerge cherry-pick has conflicts?

The skill stops and prints the release PR URL, the current git status, and resume instructions. After resolving conflicts, run git cherry-pick --continue and invoke /sdk-backmerge --resume.