Create pull requests for bluetooth-devices/dbus-fast. An agent skill from Bluetooth-Devices/dbus-fast.

MITAuto-check: notesDevelopment

Install PR Workflow

skills CLI
$ npx skills add Bluetooth-Devices/dbus-fast --skill pr-workflow -a claude-code

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

GitHub CLI
$ gh skill install Bluetooth-Devices/dbus-fast pr-workflow --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/Bluetooth-Devices/dbus-fast.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/pr-workflow .claude/skills/pr-workflow && 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
pr-workflow
GitHub stars
100
Token cost
~1.3k tokens
SKILL.md length
564 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Create pull requests for bluetooth-devices/dbus-fast. An agent skill from Bluetooth-Devices/dbus-fast.

  • Works in 6 steps: Create branch from origin/main → Conventional Commits — PR title is what… → There is no PR template → …
  • Submitting changes
  • SKILL.md covers 1. Create branch from…, 2. Conventional Commits — PR…, 3. There is no PR template and 4. Commit hygiene, plus 2 more sections
  • Calls git and gh

What it does

PR Workflow is an agent skill from Bluetooth-Devices/dbus-fast. Create pull requests for bluetooth-devices/dbus-fast. Use when creating PRs, submitting changes, or preparing contributions.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. The repository describes itself as: A faster version of dbus-next. The licence is MIT.

When your agent uses it

  • Submitting changes
  • Preparing contributions

Example prompts

  • “/pr-workflow”

Requirements

  • Python 3
  • Pre-approved tools (allowed-tools): Read, Bash, Glob, Grep

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Create branch from origin/main
  2. Conventional Commits — PR title is what matters
  3. There is no PR template
  4. Commit hygiene
  5. Push and create the PR
  6. After the PR is open

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash
    • Glob
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

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

  • Network

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

PR Workflow loads about 1.3k tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 564 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~34
When it runs · the whole SKILL.md, loaded when a task matches
~1.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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Bash, Glob, Grep

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 Bluetooth-Devices/dbus-fast at commit 59d715a, republished under its MIT licence (© Bluetooth-Devices). 564 words, ~1,296 tokens.

Download SKILL.mdSave it as .claude/skills/pr-workflow/SKILL.md (or your agent's skills folder).
name
pr-workflow
description
Create pull requests for bluetooth-devices/dbus-fast. Use when creating PRs, submitting changes, or preparing contributions.
allowed-tools
Read, Bash, Glob, Grep

dbus-fast PR Workflow

When creating a pull request for bluetooth-devices/dbus-fast, follow these steps. Repo-wide conventions live in CLAUDE.md; this skill summarises the parts that matter at PR-creation time.

1. Create branch from origin/main

origin points at bluetooth-devices/dbus-fast; there is no fork in this workflow. Always re-fetch first so the branch is based on the latest main:

bash
git fetch origin
git checkout -b <branch-name> origin/main

2. Conventional Commits — PR title is what matters

The repo is squash-merge only with squash_merge_commit_title = PR_TITLE, so the PR title becomes the subject of the commit that lands on main. The pr-title.yml workflow runs amannn/action-semantic-pull-request against the title and is the sole CI gate on its format — individual commits on the branch are discarded by the squash, so CI no longer lints them. The local commitizen pre-commit hook still flags per-commit subjects at commit time as a convenience.

Accepted types: build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test. Scope is optional. The subject (text after type(scope):) must start lowercase. Examples that pass:

feat: add async context manager to MessageBus
fix(unmarshaller): handle empty arrays at end of frame
perf!: drop python 3.9 support

A mis-formatted PR title fails pr-title.yml; fix it in the GitHub UI (or with gh pr edit --title) — no push is needed.

Pick the type that matches the release impact

python-semantic-release reads the commit log on main to decide the next version and write CHANGELOG.md:

TypeRelease effect
feat:minor bump, shows in changelog under Features
fix:, perf:patch bump, shows under Bug Fixes / Performance
any with ! or BREAKING CHANGE: footermajor bump
chore:, docs:, test:, ci:, style:, build:, refactor:no bump

A user-visible bugfix tagged chore: will be silently omitted from the changelog; an internal refactor tagged feat!: will mint a fake major release. Pick the type a changelog reader would expect.

3. There is no PR template

The repo does not ship a .github/PULL_REQUEST_TEMPLATE.md, so the PR body is freeform. Write a short description of:

  • What the change does (one or two sentences of prose).
  • Why — the motivating bug, benchmark, or feature ask.
  • Linked issues — fixes #N / closes #N for issue closure, or a bare reference if the change is related but doesn't close.

Keep it focused; the commit messages carry the per-commit detail.

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

4. Commit hygiene

  • Imperative-mood subject line — "Add X", not "Added X".

  • No Co-Authored-By trailers for LLM tools. Project preference — commits attribute the human who reviewed the change.

  • Let pre-commit run (ruff lint + format, pyupgrade, trailing-whitespace, etc.). If a hook auto-fixes a file, the commit aborts — re-stage the auto-fixed files and re-commit.

  • Write tests for behavioural changes (under tests/). Run them under dbus-run-session since the suite needs a session bus:

    bash
    dbus-run-session -- poetry run pytest --timeout=5

5. Push and create the PR

bash
git push -u origin <branch-name>
gh pr create --repo bluetooth-devices/dbus-fast --base main \
  --title "type(scope): lowercase subject under ~70 chars" \
  --body-file /tmp/pr-body.md

Use --body-file rather than --body "..." so that backticks, asterisks, and other Markdown in the body are passed through verbatim instead of being mangled by shell quoting.

6. After the PR is open

CI runs:

  • lint — pre-commit (ruff lint + format, pyupgrade, trailing-whitespace).
  • pr-title — PR-title Conventional Commits check (the only commit-format gate; individual commits are squashed away on merge).
  • test matrix — Python 3.11–3.15 + 3.14t and 3.15t, each in both SKIP_CYTHON=1 and REQUIRE_CYTHON=1 modes.
  • test_big_endian — s390x via uraimo/run-on-arch-action, catches endian regressions in the marshaller/unmarshaller.
  • benchmark — CodSpeed run for the hot paths.

A red test_big_endian job almost always means a byte-order assumption leaked into the marshaller/unmarshaller — re-check any struct format strings and endian conversions in src/dbus_fast/_private/. A CodSpeed regression on a Cythonized path is worth investigating before merge; if the regression is intentional, call it out in the PR body so reviewers don't have to guess.

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

Files

Just SKILL.md in .claude/skills/pr-workflow of Bluetooth-Devices/dbus-fast.

Open the folder on GitHubat commit 59d715a

Compare with similar skills

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

PR Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR Workflow this skillBluetooth-Devices/dbus-fast100—~1.3kAutomated safety check: NotesMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands91k—~2.4kAutomated safety check: PassMIT
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    91k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Record PR Demo

    payloadcms/payload

    A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.

    45k GitHub stars~1k tokensUpdated yesterday
    DevelopmentAuto-check passed

Categories

Questions about PR Workflow

What does PR Workflow do?

Create pull requests for bluetooth-devices/dbus-fast. An agent skill from Bluetooth-Devices/dbus-fast. PR Workflow is an agent skill from Bluetooth-Devices/dbus-fast. Create pull requests for bluetooth-devices/dbus-fast.

When should I use PR Workflow?

PR Workflow fits situations like: submitting changes; preparing contributions.

How do I install PR Workflow in Claude Code?

Run `npx skills add Bluetooth-Devices/dbus-fast --skill pr-workflow -a claude-code`. Or copy the skill folder (.claude/skills/pr-workflow in Bluetooth-Devices/dbus-fast) into .claude/skills/pr-workflow in your project. Claude Code loads it when a task matches its description.

How do I install PR Workflow in Codex?

Run `npx skills add Bluetooth-Devices/dbus-fast --skill pr-workflow -a codex`. Or copy the skill folder (.claude/skills/pr-workflow in Bluetooth-Devices/dbus-fast) into .agents/skills/pr-workflow in your project. Codex loads it when a task matches its description.

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

What does PR Workflow need to run?

Going by SKILL.md and its folder, PR Workflow needs the command-line tools its instructions call (git and gh). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Bash, Glob, Grep.

Does PR Workflow 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 PR Workflow safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does PR Workflow use?

PR Workflow 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 PR Workflow use?

About 1.3k tokens (SKILL.md is roughly 5.2k 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 PR Workflow?

Skills that share tags, products or a category with PR Workflow: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 91k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR Workflow?

Bluetooth-Devices (a GitHub organization) maintains it in Bluetooth-Devices/dbus-fast, which has 100 GitHub stars. The repository was last updated on October 5, 2026.

Source: Bluetooth-Devices/dbus-fast on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.