// Generate PR descriptions for addon packages (non-SDK inference addons, decoder, OCR). Use when creating a PR description or user asks to "prepare PR description" for an addon package.
Generate changelogs for SDK pod packages using tag-based GitFlow. Use when preparing a release, generating changelog, or creating CHANGELOG_LLM.md.
Plan and run local PR validation for tetherto/qvac PRs. Reuses the shared PR worktree, discovers touched packages and package.json scripts, recommends a test tier, and analyzes results. Use when testing a PR or invoking /qv-pr-test.
Plans and scaffolds e2e tests in packages/sdk/e2e for a new or changed public SDK API. Use when adding or modifying SDK functionality that is exposed to consumers. Enforces happy / sad / error coverage, deterministic model-output assertions, mobile/desktop placement, smoke-suite selection, and local validation with run:local.
Catalog of all repo qv-* custom skills with one-line purpose and when-to-use. Use when the user asks what skills exist, which skill to use, how to invoke a skill, or invokes /qv-skill-list.
Release a package to NPM. Validates version bump, changelog, creates release branch, monitors CI, verifies publish.
Diagnose why CI checks are not running on a PR and/or why a PR cannot be merged, by cross-referencing the live PR state (via gh CLI) against the repo's labels, teams, CODEOWNERS, label-gate trust model, and tier-based approval rules. Read-only by default — proposes labels / re-review comments / unblock actions in plan-then-apply mode. Use when a developer asks "why aren't my checks running", "why can't I merge", "what's blocking my PR", or invokes /qv-devops-why-my-pr-not with a PR URL.
| name | qv-addon-pr-create |
| description | Generate PR descriptions for addon packages (non-SDK inference addons, decoder, OCR). Use when creating a PR description or user asks to "prepare PR description" for an addon package. |
Generate PR descriptions for addon packages (non-SDK packages like inference addons, decoder, OCR). Collects changes from the remote tracked branch, validates the version bump, and fills in the PR template.
Identify the PR base/head, collect the full change set from the remote tracked branch, and validate the version bump in package.json against main:
Find the PR base and head: The base is main (or the branch configured as default). The head is the current branch.
Collect changes from the remote tracked branch:
main...origin/<current-branch> (or the PR base commit...origin/) to list commits and diffs.Mandatory version bump check:
package.json between main and origin/<current-branch>.version in package.json is unchanged compared to main, display this exact warning to the user:version in package.json is unchanged compared to main.
If this PR includes any changes that must be released in the package, you must bump the package version, commit/push it and re-run this command.Do not include uncommitted changes or untracked files: If any uncommitted/untracked files are present, or if there are local-only commits, ignore them.
If there's a release notes file in release-notes/ that matches the new version in package.json, read it for additional context. If it's missing, warn the user.
The goal is a single combined change set: all commits on the remote tracked branch vs main, while ensuring no unwanted changes end up in the PR description.
Use .github/PULL_REQUEST_TEMPLATE/addon.md as the template. If there are additional instructions in the template file, follow them too.
Fill in the template based on the combined change set. Return the completed PR description to the user as a message.
Do NOT create or modify any additional files when producing the PR description.