New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Qv Devops PR Create

by tetherto in tetherto/qvac

Generate PR titles and descriptions for DevOps surfaces (CI/CD, composite actions, automation scripts, IaC) following the devops.md PR template and commit/PR format rule.

Apache-2.0Auto-check passedDevOps & Cloud

Install Qv Devops PR Create

skills CLI
$ npx skills add tetherto/qvac --skill qv-devops-pr-create -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tetherto/qvac qv-devops-pr-create --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tetherto/qvac.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/qv-devops-pr-create .claude/skills/qv-devops-pr-create && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
qv-devops-pr-create
GitHub stars
681
Token cost
~2.3k tokens
SKILL.md length
1,046 words
Files
2
Skills in repo
50
Repo updated
First seen
Licence
Apache-2.0

At a glance

Generate PR titles and descriptions for DevOps surfaces (CI/CD, composite actions, automation scripts, IaC) following the devops.md PR template and commit/PR format rule.

  • Works in 10 steps: Confirm base and current branch — note… → Collect commits/diff from ...origin/. → Infer ticket, prefix, and tag from… → …
  • Creating a DevOps PR
  • SKILL.md covers When to use this skill, Prerequisites, Workflow and Inference Strategy, plus 7 more sections
  • Calls gh, git and terraform

What it does

Qv Devops PR Create is an agent skill from tetherto/qvac. Generate PR titles and descriptions for DevOps surfaces (CI/CD, composite actions, automation scripts, IaC) following the devops.md PR template and commit/PR format rule. Use when creating a DevOps PR or invoking /qv-devops-pr-create.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in DevOps & Cloud, covering CI/CD and Infrastructure as code. It works with GitHub. The repository describes itself as: Open-source local AI SDK - run AI on-device with no cloud, no API keys. Supports GGUF, RAG, image, music, and video generation, speech-to-text, P2P inference, and more… The licence is Apache-2.0.

When your agent uses it

  • Creating a DevOps PR
  • Invoking /qv-devops-pr-create

Example prompts

  • “/qv-devops-pr-create”

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

  1. Confirm base and current branch — note whether the base is main (default) or a release-* branch (uncommon for DevOps; treat as…
  2. Collect commits/diff from ...origin/.
  3. Infer ticket, prefix, and tag from changes (see Inference Strategy).
  4. Detect trigger sections (action pinning / permissions / plan-dry-run / breaking) and only ask the user for input when inference confidence…
  5. Generate title: TICKET prefix[tag]?: subject.
  6. Fill template sections based on changes and detected triggers.
  7. Validate tag requirements ([bc]).
  8. Save the assembled PR body to /tmp/pr-body.md so subsequent steps and any gh pr create invocation can read it back without re-rendering…
  9. Print the paste-ready commands alongside the in-chat preview — both for direct paste into the GitHub PR-create form and for clipboard tools
  10. Optionally create the PR via gh (see "gh CLI Integration" below).

What it can do on your machine

Read from SKILL.md and the folder at commit c3a6030. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git
    • terraform
    • kubectl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, git and kubectl, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Qv Devops PR Create loads about 2.3k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 1,046 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tetherto/qvac at commit c3a6030, republished under its Apache-2.0 licence (© tetherto). 1,046 words, ~2,339 tokens.

Download SKILL.mdSave it as .claude/skills/qv-devops-pr-create/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
qv-devops-pr-create
description
Generate PR titles and descriptions for DevOps surfaces (CI/CD, composite actions, automation scripts, IaC) following the devops.md PR template and commit/PR format rule. Use when creating a DevOps PR or invoking /qv-devops-pr-create.
disable-model-invocation
true

DevOps PR Creation

Generate PR titles and descriptions for DevOps changes (CI/CD workflows, composite actions, repo-wide automation scripts, IaC), following the DevOps pod's format rule and PR template.

When to use this skill

Applies to PRs whose changes are dominated by paths in .github/teams/devops.json's ownedPaths: .github/workflows/, .github/actions/, .github/scripts/, scripts/. Also applies to repo-level configuration changes (.github/CODEOWNERS, .github/dependabot.yml, top-level Dockerfiles, IaC under top-level terraform/, ansible/, k8s/).

Use when:

  • Creating a PR for any DevOps change
  • User asks to generate a DevOps PR description
  • User invokes /qv-devops-pr-create

If the touched paths are dominated by a non-DevOps pod (e.g., packages/sdk/**), use that pod's *-pr-create skill instead. If a PR mixes DevOps + package changes, prefer the package's pod skill and call out the cross-pod touches in the PR body.

Prerequisites

  • gh CLI installed and authenticated (gh auth status)
  • Branch is pushed to a fork (or the upstream when the user has write access to tetherto/qvac)
  • Local branch tracks the remote being PR'd from

Workflow

  1. Confirm base and current branch — note whether the base is main (default) or a release-* branch (uncommon for DevOps; treat as user-provided).

  2. Collect commits/diff from <base>...origin/<branch>.

  3. Infer ticket, prefix, and tag from changes (see Inference Strategy).

  4. Detect trigger sections (action pinning / permissions / plan-dry-run / breaking) and only ask the user for input when inference confidence is low.

  5. Generate title: TICKET prefix[tag]?: subject.

  6. Fill template sections based on changes and detected triggers.

  7. Validate tag requirements ([bc]).

  8. Save the assembled PR body to /tmp/pr-body.md so subsequent steps and any gh pr create invocation can read it back without re-rendering. Print the body in chat for inspection AND keep the file canonical (the gh-CLI step below reads from it).

  9. Print the paste-ready commands alongside the in-chat preview — both for direct paste into the GitHub PR-create form and for clipboard tools:

    bash
    pbcopy < /tmp/pr-body.md   # macOS
xclip -selection clipboard < /tmp/pr-body.md   # Linux
wl-copy < /tmp/pr-body.md   # Wayland

  10. Optionally create the PR via gh (see "gh CLI Integration" below).

Inference Strategy

Infer first, ask only if uncertain.

Ticket number:

  • Extract from branch name pattern: QVAC-\d+, SDK-\d+, etc.
  • Extract from commit messages if referenced.
  • ASK only if no ticket found (offer [notask] as the alternative).

Prefix (infra / feat / fix / chore / doc / test):

  • Extract from branch name prefix when present (e.g. infra/, fix/, chore/).
  • Use majority prefix from existing commit messages.
  • If no conventional commits, infer from diff:
    • .github/workflows/**, .github/actions/**, .github/scripts/**, scripts/**, IaC files, Dockerfiles, runner config → infra
    • New skill / new workflow type / new composite action → feat
    • Bug-related changes (commit messages mention "fix", "broken", "regression"; reverts) → fix
    • Only .md / docs files → doc
    • Only test files (.github/actions/*-test/**, *.test.*, tests/**) → test
    • Pure dependency bumps / deprecations / lockfile churn → chore
  • ASK only on mixed signals.

Tag ([bc] / [notask] / [skiplog] — not combinable):

  • [bc] (breaking change) when the diff:
    • Renames a job whose name is referenced by a branch protection ruleset (status check rename)
    • Changes a reusable workflow's inputs: / outputs: shape (workflow_call signature)
    • Changes a composite action's inputs: / outputs: shape (.github/actions/<name>/action.yml)
    • Changes a workflow_call secrets: or permissions: contract
    • Removes a slash command / public surface from a skill that other teams consume
  • [notask] (PRs only): when no ticket — minor automation hygiene. Ask the user before applying.
  • [skiplog]: only when the user explicitly asks (this repo uses [skiplog] to opt out of changelog generation; not the default for DevOps).

ASK if [bc] is ambiguous.

Trigger detection (drives required template sections)

Walk the diff before assembling the body. For each trigger detected, the corresponding section is REQUIRED in the PR body.

TriggerDetection signalRequired section
Third-party action added / bumped / repinnedgit diff shows a uses: <vendor>/<action>@<sha> change in any .github/workflows/** or .github/actions/**/action.yml"🔐 Action pinning" with before/after SHA + version
Top-level or per-job permissions: block added / modified / removedgit diff shows ^[+-].*permissions: or `^[+-]\s+(contentspull-requests
State-changing opAny of: terraform/** *.tf, ansible/** *.yml, k8s/** *.yaml, gh ruleset edit invocations, branch-protection patches"📋 Plan / dry-run output" — paste the plan/diff
Breaking change[bc] tag set per Inference Strategy"💥 Breaking changes" with BEFORE/AFTER YAML blocks

Sections that are NOT triggered MUST be deleted (per the template's "Delete this section if not applicable" markers).

Show full SKILL.md (376 more words)Show less

Format References

  • PR title format: see the Validation regex below — ^([A-Z]+-\d+ )?(infra|feat|fix|chore|doc|test)(\[(bc|notask|skiplog)\])?: \S.+$
  • PR body template: .github/PULL_REQUEST_TEMPLATE/devops.md
  • GitHub and CI guidance (including conventions that drive "How was it tested?" content): .github/AGENTS.md

Fill the template based on the diff analysis. Delete sections that don't apply.

Output Format

ALWAYS output the PR in this copy-ready format, even when making corrections:

## PR Title
```
TICKET prefix[tag]?: subject
```

## PR Body
```markdown
## 🎯 What problem does this PR solve?
...
```

Validation

No pr-validation-devops.yml workflow exists yet (the SDK-pod validator is paths-scoped to packages/<pkg>/). This skill MUST validate the title client-side before pushing or invoking gh pr create. Refuse and ask for correction if any of these fail:

  • Title regex: ^([A-Z]+-\d+ )?(infra|feat|fix|chore|doc|test)(\[(bc|notask|skiplog)\])?: \S.+$
  • Lowercase prefix and lowercase subject (sentence case allowed; the first word may be capitalized for proper nouns)
  • A ticket prefix (QVAC-\d+) is present unless [notask] is used
  • For [bc]: body contains a "💥 Breaking changes" section with BEFORE/AFTER fenced blocks
  • For an action-pinning trigger: body contains a "🔐 Action pinning" section
  • For a permissions trigger: body contains a "🛡️ Permissions changes" section
  • For an IaC/state-changing trigger: body contains a "📋 Plan / dry-run output" section

gh CLI Integration

After generating the PR description, check for gh and offer to create the PR:

  1. which gh — confirm CLI is installed
  2. git remote -v — identify whether origin is the upstream (tetherto/qvac) or a fork
  3. Ask the user: "Create PR now with gh CLI?" [Yes / No / Preview first]
  4. If yes, ensure changes are committed and pushed first
  5. Create PR with explicit base/head; for fork workflows, pass --repo, --base, --head:
bash
gh pr create \
  --repo tetherto/qvac \
  --base main \
  --head <fork-owner>:<branch> \
  --title "TICKET infra: subject" \
  --body "$(cat /tmp/pr-body.md)"

For direct-push workflows (the user has write to tetherto/qvac):

bash
gh pr create \
  --base main \
  --title "TICKET infra: subject" \
  --body "$(cat /tmp/pr-body.md)"
  1. Print the resulting PR URL as a clickable hyperlink.

Never run gh pr create --web for this skill — --web does not actually create the PR; it only opens the browser. The body we generated would be lost.

Quality Checklist

Before outputting, verify:

  • Title matches the regex above
  • "What problem" describes operator/user impact, not implementation
  • "How it solves" is high-level approach, not line-by-line
  • "How was it tested?" lists concrete validation steps (actionlint clean, workflow_dispatch test run, terraform plan output, kubectl diff output, etc.)
  • Untriggered template sections are deleted
  • [bc] body has BEFORE/AFTER YAML blocks
  • Action-pinning trigger → action-pinning section present
  • Permissions trigger → permissions section present
  • State-changing trigger → plan/dry-run section present

References

© tetherto, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/qv-devops-pr-create of tetherto/qvac.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit c3a6030

Compare with similar skills

Qv Devops PR Create next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Qv Devops PR Create compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Qv Devops PR Create this skilltetherto/qvac681—~2.3kAutomated safety check: PassApache-2.0
Admingrafana/skills279—~1.5kAutomated safety check: PassApache-2.0
AWS GitHub Oidc Scoped Rolemizchi/skills356—~1.6kAutomated safety check: PassNone
Devops Pipelineluongnv89/skills131—~4.8kAutomated safety check: PassMIT
Sdaf Plan And Test SemanticsAzure/sap-automation145—~1.6kAutomated safety check: PassMIT
Oraclecloud CI Integrationjeremylongshore/tons-of-skills-marketplace2.8k—~2kAutomated safety check: PassMIT

Similar skills

  • Admin

    grafana/skills

    Official

    Manage Grafana Cloud accounts — organizations, stacks, RBAC roles and assignments, SSO/SAML/OAuth/GitHub auth, service accounts for CI/CD, user invites, team membership, and API-driven provisioning.

    279 GitHub stars~1.5k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • AWS GitHub Oidc Scoped Role

    mizchi/skills

    OpenTofu/Terraform pattern for GitHub Actions OIDC trust with AWS IAM.

    356 GitHub stars~1.6k tokensUpdated 5 days ago
    DevOps & CloudAuto-check passed

  • Devops Pipeline

    luongnv89/skills

    Configure pre-commit hooks and lean GitHub Actions for shift-left quality assurance.

    131 GitHub stars~4.8k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Sdaf Plan And Test Semantics

    Azure/sap-automation

    Official

    Explain SDAF plan-only / test / apply semantics without pretending they are universal.

    145 GitHub stars~1.6k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Oraclecloud CI Integration

    jeremylongshore/tons-of-skills-marketplace

    Configure CI/CD pipelines for OCI with Terraform and GitHub Actions.

    2.8k GitHub stars~2k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Terraform and OpenTofu Guide

    agentscope-ai/QwenPaw

    Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.

    35k GitHub starsUsed in 6 repos~4.2k tokens
    DevOps & CloudAuto-check passed

More from tetherto/qvac

All 50 skills in this repo

  • Qv Docs Solution Create

    tetherto/qvac

    Creates a Solutions page in the QVAC documentation website from a real use case, generalizing the case into reusable guidance and registering the page in the site navigation.

    681 GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • Qv Docs Update

    tetherto/qvac

    Updates the docs website after a change to the SDK or CLI. An agent skill from tetherto/qvac.

    681 GitHub stars~11k tokensUpdated today
    Auto-check passed

  • Qv Agent Stack Sync

    tetherto/qvac

    Plan and prepare the QVAC agent-stack release cascade across @qvac/inference, @qvac/sdk, @qvac/cli, @qvac/ai-sdk-provider, @qvac/opencode-plugin, and @qvac/openclaw-plugin.

    681 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Qv Quality Reporting

    tetherto/qvac

    Run the deterministic code-quality audit, turn related findings into contextual remediation groups, prepare approval-gated Asana proposals, reconcile recurring runs, or configure twice-monthly…

    681 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Cpp String API Review

    tetherto/qvac

    Review C++ changes for string parameter and call-site efficiency conventions (std::stringview, std::string&&, const std::string&, const char, and TransparentStringMap lookup).

    681 GitHub stars~702 tokensUpdated today
    Auto-check passed

  • Qv Addon Changelog

    tetherto/qvac

    Generate changelog entries for a target add-on package. An agent skill from tetherto/qvac.

    681 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Qv Devops PR Create

What does Qv Devops PR Create do?

Generate PR titles and descriptions for DevOps surfaces (CI/CD, composite actions, automation scripts, IaC) following the devops.md PR template and commit/PR format rule. Qv Devops PR Create is an agent skill from tetherto/qvac.md PR template and commit/PR format rule.

When should I use Qv Devops PR Create?

Qv Devops PR Create fits situations like: creating a DevOps PR; invoking /qv-devops-pr-create.

How do I install Qv Devops PR Create in Claude Code?

Run `npx skills add tetherto/qvac --skill qv-devops-pr-create -a claude-code`. Or copy the skill folder (.agents/skills/qv-devops-pr-create in tetherto/qvac) into .claude/skills/qv-devops-pr-create in your project. Claude Code loads it when a task matches its description.

How do I install Qv Devops PR Create in Codex?

Run `npx skills add tetherto/qvac --skill qv-devops-pr-create -a codex`. Or copy the skill folder (.agents/skills/qv-devops-pr-create in tetherto/qvac) into .agents/skills/qv-devops-pr-create in your project. Codex loads it when a task matches its description.

Can I use Qv Devops PR Create in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tetherto/qvac --skill qv-devops-pr-create -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qv-devops-pr-create, .gemini/skills/qv-devops-pr-create, .github/skills/qv-devops-pr-create and .opencode/skills/qv-devops-pr-create in your project.

What does Qv Devops PR Create need to run?

Going by SKILL.md and its folder, Qv Devops PR Create needs the command-line tools its instructions call (gh, git, terraform and kubectl).

Does Qv Devops PR Create access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Qv Devops PR Create safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Qv Devops PR Create use?

Qv Devops PR Create is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Qv Devops PR Create use?

About 2.3k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Qv Devops PR Create?

Skills that share tags, products or a category with Qv Devops PR Create: Admin (grafana/skills, 279 stars), AWS GitHub Oidc Scoped Role (mizchi/skills, 356 stars), Devops Pipeline (luongnv89/skills, 131 stars) and Sdaf Plan And Test Semantics (Azure/sap-automation, 145 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Qv Devops PR Create?

tetherto (a GitHub organization) maintains it in tetherto/qvac, which has 681 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 7, 2026.

Source: tetherto/qvac on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.