addon-pr-create

Generate PR descriptions for addon packages from remote branch changes and version bump validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing pull request descriptions for addon packages (inference addons, decoder, OCR) is repetitive and error-prone, especially when you must collect the full change set from the remote tracked branch and remember to verify the package version bump before release. ## Core Features & Use Cases - Change Set Collection: Compares main...origin/<current-branch> to gather all commits and diffs from the remote tracked branch only, ignoring uncommitted or untracked local changes. - Version Bump Validation: Compares package.json between main and the remote branch and displays a mandatory warning if the version is unchanged. - Template-Based Generation: Fills in .github/PULL_REQUEST_TEMPLATE/addon.md and optionally incorporates matching release notes from release-notes/. - Use Case: You finished work on an OCR addon branch and pushed it. Ask for a PR description and receive a completed template based on the actual remote commits, plus a warning if you forgot to bump the package version. ## Quick Start Ask the assistant to prepare a PR description for the current addon package branch.

Frequently Asked Questions about addon-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 addon package?

Ask the assistant to prepare a PR description while on your addon branch. It collects commits and diffs from the remote tracked branch versus main, then fills in the addon pull request template and returns the completed description.

How to check if a package version bump is needed before a PR?

The workflow compares package.json between main and the remote branch automatically. If the version field is unchanged, it displays a warning telling you to bump the version, commit, push, and re-run before releasing.

Does the PR description include uncommitted or untracked changes?

No. Only the remote tracked branch is considered when building the change set. Uncommitted changes, untracked files, and local-only commits are explicitly ignored so the description matches what reviewers will see.

What happens if release notes are missing for the new version?

If no file in release-notes/ matches the new version in package.json, the workflow warns you but still proceeds. When the file exists, its content is read and used as additional context for the PR description.

Which packages does this PR description workflow support?

It targets non-SDK addon packages such as inference addons, decoder, and OCR packages. It uses the addon-specific pull request template located at .github/PULL_REQUEST_TEMPLATE/addon.md.