agentleFS
Sign inStart free
tethertotetherto/qvac/.agents/skills/qv-addon-pr-create/SKILL.md

qv-addon-pr-create

Skill697 starsChanged 18 days agoApache-2.0View on GitHub

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.

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    If the version in package.json is unchanged compared to main, display this exact warning to the user:

    line 29
  2. Distinctive:

    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 …

    line 34
  3. Distinctive:

    Do not include uncommitted changes or untracked files: If any uncommitted/untracked files are present, or if there are local-only commits, …

    line 39
  4. Very specific:

    If there's a release notes file in release-notes/ that matches the new version in package.json, read it for additional context.

    line 40
  5. Very specific:

    Use .github/PULL_REQUEST_TEMPLATE/addon.md as the template.

    line 46
  6. Distinctive:

    Do NOT create or modify any additional files when producing the PR description.

    line 50
  7. Very specific:

    Do not add packages/cli to a native addon PR.

    line 52

≈ “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

Addon PR Description Generator

What

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.

When to Use

  • Creating a PR description for an addon package
  • User explicitly asks to "generate a PR description" or "prepare PR description" while working in an addon package

Instructions

Step 1: Identify base/head, collect changes, and verify version bump

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:

  1. Find the PR base and head: The base is main (or the branch configured as default). The head is the current branch.
  2. Collect changes from the remote tracked branch:
    • Compare main...origin/<current-branch> (or the PR base commit...origin/<current-branch>) to list commits and diffs.
    • The rule: only the remote tracked branch is considered.

  3. Mandatory version bump check:

    • Always compare package.json between main and origin/<current-branch>.
    • If the version in package.json is unchanged compared to main, display this exact warning to the user:

    WARNING: VERSION BUMP MAY BE REQUIRED The 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.

    • Still proceed with the next steps
  4. Do not include uncommitted changes or untracked files: If any uncommitted/untracked files are present, or if there are local-only commits, ignore them.
  5. 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.

Step 2: Generate 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.

Do not add packages/cli to a native addon PR. If a follow-up SDK exposure PR is expected, remind the author that CLI belongs there (see packages/sdk/AGENTS.md).

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