New: 97,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

Open PR

by druxt in druxt/druxt.js

Prepares and opens a druxt.js pull request from a contributor's fork against develop, with a Conventional Commits title and the repository's template filled in.

MITAuto-check passedDevelopment

Install Open PR

skills CLI
$ npx skills add druxt/druxt.js --skill open-pr -a claude-code

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

GitHub CLI
$ gh skill install druxt/druxt.js open-pr --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/druxt/druxt.js.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/open-pr .claude/skills/open-pr && 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
open-pr
GitHub stars
114
Token cost
~771 tokens
SKILL.md length
397 words
Files
2
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Prepares and opens a druxt.js pull request from a contributor's fork against develop, with a Conventional Commits title and the repository's template filled in.

  • Works in 5 steps: The verify-change skill has passed in… → A changeset is committed when the… → The commits follow Conventional Commits,… → …
  • A druxt.js change is ready for review
  • SKILL.md covers Before opening, Title, Description and Open it, plus 1 more section
  • Calls git, gh and yarn

What it does

Open PR is an agent skill from druxt/druxt.js. Prepares and opens a druxt.js pull request from a contributor's fork against develop, with a Conventional Commits title and the repository's template filled in. Use when a druxt.js change is ready for review, or when asked to open a pull request or to write its title or description.

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

It sits in Development, covering Pull requests and Commit messages. It works with Nuxt. The repository describes itself as: The Fully Decoupled Drupal Framework. The licence is MIT.

When your agent uses it

  • A druxt.js change is ready for review
  • Asked to open a pull request
  • Write its title

Example prompts

  • “Use the open-pr skill to prepare and opens a druxt.js pull request from a contributor's fork against develop, with a Conventional Commits title and…”
  • “/open-pr”

Workflow steps

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

  1. The verify-change skill has passed in this session, and you have its output.
  2. A changeset is committed when the add-changeset skill says the change needs one. A fix for a bug that no release has needs none, even in a…
  3. The commits follow Conventional Commits, scoped by the issue number when there is one and by the package name otherwise. The commit-msg…
  4. The branch is up to date with develop. Merge upstream/develop into it, then re-run the gate.
  5. The commits are authored and committed under the git identity of the person you work for, not an agent's. Their messages carry no AI…

What it can do on your machine

Read from SKILL.md and the folder at commit b07a3e3. 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:

    • git
    • gh
    • yarn

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

  • Network

    No URLs in SKILL.md. Its commands use git, gh and yarn, 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

Open PR loads about 771 tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 397 words of instructions outside code blocks.

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

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 druxt/druxt.js at commit b07a3e3, republished under its MIT licence (© druxt). 397 words, ~771 tokens.

Download SKILL.mdSave it as .claude/skills/open-pr/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
open-pr
description
Prepares and opens a druxt.js pull request from a contributor's fork against develop, with a Conventional Commits title and the repository's template filled in. Use when a druxt.js change is ready for review, or when asked to open a pull request or to write its title or description.

Open a pull request

Pull requests go from a branch on your fork to develop on druxt/druxt.js. Push and open one only when the person you work for asks you to.

Before opening

  1. The verify-change skill has passed in this session, and you have its output.
  2. A changeset is committed when the add-changeset skill says the change needs one. A fix for a bug that no release has needs none, even in a published package.
  3. The commits follow Conventional Commits, scoped by the issue number when there is one and by the package name otherwise. The commit-msg hook enforces the format, so let it run.
  4. The branch is up to date with develop. Merge upstream/develop into it, then re-run the gate.
  5. The commits are authored and committed under the git identity of the person you work for, not an agent's. Their messages carry no AI attribution lines. yarn lint:commit --from upstream/develop --to HEAD checks the messages, and the pre-push hook checks the identity too.

Title

Pull requests are squash merged, and the title becomes the commit on develop. Write it as a Conventional Commits subject that says what changes for a Druxt user:

text
fix(#412): render nothing for a menu with no items
feat(router): resolve paths with a trailing slash

The scope is the issue number when there is one (fix(#412): …), and otherwise the package directory name (menu, router, druxt). Leave the scope out for a change across several packages with no issue.

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

Description

Fill in every section of .github/PULL_REQUEST_TEMPLATE.md:

  • Types of changes: tick the boxes that apply.
  • Description: what changed and why, with a Resolves: #123 line for the issue. Include the spec when there is one, and list the commands you ran to verify the change with their results.
  • Checklist: tick only what is true. If a box does not apply, say why.
  • Screenshots/Media: add these for anything visible in a browser.

Ask a maintainer for the perf-audit label when the change touches a store, the Druxt client, a Nuxt module or how components fetch data. The audit then posts its numbers on the pull request.

Open it

bash
git push -u origin <branch>
gh pr create --repo druxt/druxt.js --base develop --head <your-user>:<branch> \
  --title "fix(#412): render nothing for a menu with no items" --body-file <description.md>

Without the gh CLI, open the compare page that git push prints.

After opening

CI runs on the pull request. A red check is yours to fix before review starts, using the address-review skill. Maintainers review, label and merge. Never merge a pull request, even when asked: a maintainer does that. Leave labels and reviewer requests to them too.

© druxt, MIT. 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/open-pr of druxt/druxt.js.

  • SKILL.md
  • evals/tests.yaml

Open the folder on GitHubat commit b07a3e3

Compare with similar skills

Open PR 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.

Open PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Open PR this skilldruxt/druxt.js114—~771Automated safety check: PassMIT
PR Finalize Reviewmicrosoft/garnet12k—~3.1kAutomated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills102k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Emoji Commit ConventionsbaptisteArno/typebot.io11k—~424Automated safety check: PassCustom licence

Similar skills

  • PR Finalize Review

    microsoft/garnet

    Official

    Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.

    12k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    102k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Emoji Commit Conventions

    baptisteArno/typebot.io

    Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.

    11k GitHub stars~424 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Commit And PR Messages

    superplanehq/superplane

    Write Git commit messages and pull request titles/descriptions using the Chris Beams / Tim Pope conventions (subject/body split, ~50-char subject, imperative mood, why-not-how body) plus ASD-STE100…

    7.7k GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed

More from druxt/druxt.js

  • Add Changeset

    druxt/druxt.js

    Writes the changeset that versions a druxt.js package change and becomes its changelog entry.

    114 GitHub stars~763 tokensUpdated today
    Auto-check passed

  • Address Review

    druxt/druxt.js

    Works through review comments and failing CI on a druxt.js pull request, fixing or answering each one until the pull request is green and every thread has a reply.

    114 GitHub stars~600 tokensUpdated today
    Auto-check passed

  • Start Work

    druxt/druxt.js

    Sets up a druxt.js change before the first edit, from the issue to a feature branch off develop, a short spec and a failing test.

    114 GitHub stars~887 tokensUpdated today
    Auto-check passed

  • Triage Issue

    druxt/druxt.js

    Sorts a druxt.js issue by type and package, and reproduces it against the example Drupal backend or with a failing unit test before writing up the findings.

    114 GitHub stars~763 tokensUpdated today
    Auto-check passed

  • Verify Change

    druxt/druxt.js

    Runs the druxt.js verification gate (lint, build, unit tests and the checks for whatever else changed) and reports the real results.

    114 GitHub stars~916 tokensUpdated today
    Auto-check passed

  • Write Skill

    druxt/druxt.js

    Creates or changes a druxt.js contributor skill in .agents/skills, with its evals and the tests that gate it.

    114 GitHub stars~926 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Open PR

What does Open PR do?

Prepares and opens a druxt.js pull request from a contributor's fork against develop, with a Conventional Commits title and the repository's template filled in. js.js pull request from a contributor's fork against develop, with a Conventional Commits title and the repository's template filled in.

When should I use Open PR?

Open PR fits situations like: A druxt.js change is ready for review; asked to open a pull request; write its title.

How do I install Open PR in Claude Code?

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

How do I install Open PR in Codex?

Run `npx skills add druxt/druxt.js --skill open-pr -a codex`. Or copy the skill folder (.agents/skills/open-pr in druxt/druxt.js) into .agents/skills/open-pr in your project. Codex loads it when a task matches its description.

Can I use Open PR 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 druxt/druxt.js --skill open-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/open-pr, .gemini/skills/open-pr, .github/skills/open-pr and .opencode/skills/open-pr in your project.

What does Open PR need to run?

Going by SKILL.md and its folder, Open PR needs the command-line tools its instructions call (git, gh and yarn).

Does Open PR access the network?

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

Is Open PR 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 Open PR use?

Open PR is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Open PR use?

About 771 tokens (SKILL.md is roughly 3.1k 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 Open PR?

Skills that share tags, products or a category with Open PR: PR Finalize Review (microsoft/garnet, 12k stars), Git Workflow and Versioning (addyosmani/agent-skills, 102k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars) and Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Open PR?

druxt (a GitHub organization) maintains it in druxt/druxt.js, which has 114 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.

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