Creating Description For Gh PR
redis/jedis
Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.
Rules for preparing pull requests and commits in the Quarkus project: title conventions, description format, commit hygiene, labels, and contribution policies.
Install Pull Requests
$ npx skills add quarkusio/quarkus --skill pull-requests -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install quarkusio/quarkus pull-requests --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/quarkusio/quarkus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pull-requests .claude/skills/pull-requests && rm -rf skills-srcUse ~/.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/
Install the "pull-requests" agent skill from https://github.com/quarkusio/quarkus/tree/main/.agents/skills/pull-requests into .claude/skills/pull-requests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pull-requests", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/quarkusio/quarkus/tree/main/.agents/skills/pull-requestsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add quarkusio/quarkus --skill pull-requests -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install quarkusio/quarkus pull-requests --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/quarkusio/quarkus.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/pull-requests .agents/skills/pull-requests && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pull-requests" agent skill from https://github.com/quarkusio/quarkus/tree/main/.agents/skills/pull-requests into .agents/skills/pull-requests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pull-requests", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add quarkusio/quarkus --skill pull-requests -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install quarkusio/quarkus pull-requests --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/quarkusio/quarkus.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/pull-requests .cursor/skills/pull-requests && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pull-requests" agent skill from https://github.com/quarkusio/quarkus/tree/main/.agents/skills/pull-requests into .cursor/skills/pull-requests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pull-requests", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/quarkusio/quarkus.git --path .agents/skills/pull-requests--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add quarkusio/quarkus --skill pull-requests -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install quarkusio/quarkus pull-requests --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/quarkusio/quarkus.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/pull-requests .gemini/skills/pull-requests && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pull-requests" agent skill from https://github.com/quarkusio/quarkus/tree/main/.agents/skills/pull-requests into .gemini/skills/pull-requests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pull-requests", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install quarkusio/quarkus pull-requestsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add quarkusio/quarkus --skill pull-requests -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/quarkusio/quarkus.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/pull-requests .github/skills/pull-requests && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pull-requests" agent skill from https://github.com/quarkusio/quarkus/tree/main/.agents/skills/pull-requests into .github/skills/pull-requests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pull-requests", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add quarkusio/quarkus --skill pull-requests -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install quarkusio/quarkus pull-requests --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/quarkusio/quarkus.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/pull-requests .opencode/skills/pull-requests && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pull-requests" agent skill from https://github.com/quarkusio/quarkus/tree/main/.agents/skills/pull-requests into .opencode/skills/pull-requests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pull-requests", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pull-requests- GitHub stars
- 16k
- Token cost
- ~840 tokens
- SKILL.md length
- 399 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Rules for preparing pull requests and commits in the Quarkus project: title conventions, description format, commit hygiene, labels, and contribution policies.
- Works in 3 steps: What breaks → Why it was necessary → How users should migrate
- Tasks that involve Pull requests
- SKILL.md covers PR Title, PR Description, Commits and Labels, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Pull Requests is an agent skill from quarkusio/quarkus. Rules for preparing pull requests and commits in the Quarkus project: title conventions, description format, commit hygiene, labels, and contribution policies.
Its SKILL.md is about 840 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. It works with Java. The repository describes itself as: Quarkus: Supersonic Subatomic Java. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Pull requests
Example prompts
- “Use the pull-requests skill to rule for preparing pull requests and commits in the Quarkus project: title conventions, description format, commit…”
- “/pull-requests”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- What breaks
- Why it was necessary
- How users should migrate
What it can do on your machine
Read from SKILL.md and the folder at commit 31ef64b. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Pull Requests loads about 840 tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 399 words of instructions outside code blocks.
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 quarkusio/quarkus at commit 31ef64b, republished under its Apache-2.0 licence (© quarkusio). 399 words, ~840 tokens.
Download SKILL.mdSave it as
.claude/skills/pull-requests/SKILL.md (or your agent's skills folder).- name
- pull-requests
- description
- Rules for preparing pull requests and commits in the Quarkus project: title conventions, description format, commit hygiene, labels, and contribution policies.
Pull Requests
PR Title
Write a clear, natural-language sentence that describes the change:
- Start with an uppercase letter
- Do not prefix with
feat:,fix:,chore:,docs:,refactor:, or any other Conventional Commits type — the Quarkus bot will flag this - Keep it concise but descriptive
- Do not end with a period
Examples
Add multipart upload support to RESTEasy Reactive
Fix NPE when config property is unset
Update OIDC provider configuration guide
Simplify bean resolution logic in ArCPR Description
- Explain why the change is needed, not what changed (the diff shows that)
- Keep it concise — a short paragraph is usually enough
- Do not include a "Test plan" or "Summary" section
- Do not include "Generated with Claude Code" or similar footers
- Do not include
Co-Authored-Bytrailers referencing an AI tool
Noteworthy features
If your PR introduces a noteworthy feature, include a single line at the end of
the description prefixed with Release note: that can be used verbatim in the
release notes. Keep it user-facing — focus on the benefit, not the implementation:
Release note: RESTEasy Reactive now supports multipart file uploads with
progress tracking via the new `@PartProgress` annotation.Only do this for noteworthy features, not small enhancements or bug fixes
Breaking changes
If the change is breaking, explain in the description:
- What breaks
- Why it was necessary
- How users should migrate
Commits
- Commits must be atomic and semantic — each commit should represent one logical change
- Properly squash fixup commits before the PR is ready for merge. Fixup commits are acceptable during review, but must be squashed at the end
- Write commit messages as clear, natural-language sentences starting with an uppercase letter — same style as the PR title
- Do not add
Co-Authored-Bytrailers referencing AI tools (e.g.Co-Authored-By: Claude,Co-Authored-By: Copilot)
Show full SKILL.md (149 more words)Show less
Labels
Apply these labels when relevant:
| Label | When to apply |
|---|---|
release/noteworthy-feature | The PR introduces a significant user-facing feature that should appear in release notes |
release/breaking-change | The PR contains a breaking change (API removal, behavior change, config rename) |
Before Submitting
- Run
./mvnw process-sourceson changed modules to fix formatting - Run tests in Java mode (
./mvnw verify -f extensions/<name>/) - For non-trivial changes, test in native mode (
-Dnative) - If adding a new integration test module, register it in
.github/native-tests.json - Update documentation in
docs/src/main/asciidoc/when the change affects user-facing behavior, config, or APIs
LLM / Agent Policy
- You are responsible for validating every change you submit — AI-assisted or not
- Do not submit code, tests, or descriptions copied directly from an LLM without human review
- AI-generated tests must validate actual behavior, not just exercise code paths
- Do not use bots or agents to open PRs without human authorship and responsibility
© quarkusio, 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
Just SKILL.md in .agents/skills/pull-requests of quarkusio/quarkus.
Open the folder on GitHubat commit 31ef64b
Compare with similar skills
Pull Requests 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pull Requests this skillquarkusio/quarkus | 16k | — | ~840 | Automated safety check: Pass | Apache-2.0 | |
| Creating Description For Gh PRredis/jedis | 12k | — | ~838 | Automated safety check: Pass | MIT | |
| Code Review Skillawesome-skills/code-review-skill | 2.1k | — | ~2.8k | Automated safety check: Notes | MIT | |
| CI Act Runchewiebug/GCViewer | 4.6k | — | ~2.4k | Automated safety check: Notes | Custom licence | |
| CI Script Only Runchewiebug/GCViewer | 4.6k | — | ~690 | Automated safety check: Pass | Custom licence | |
| Rota Update Importoracle/graalpython | 1.7k | — | ~475 | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Code Review Skill
awesome-skills/code-review-skill
Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C/.NET, Kotlin, Swift, Dart…
CI Act Run
chewiebug/GCViewer
Run the full build-and-deploy.yaml workflow locally via act + Docker.
CI Script Only Run
chewiebug/GCViewer
Simulate GCViewer CI paths (pull request, develop snapshot, master release) with DRYRUN and selectable OpenJDK 8/17/21/25.
- Official
Rota Update Import
oracle/graalpython
Run the GraalPy ROTA import update workflow. An agent skill from oracle/graalpython.
Code Review Excellence
andrew-yangy/gru-ai
Provides comprehensive code review guidance for React 19, Vue 3, Rust, TypeScript, Java, Python, and C/C++.
More from quarkusio/quarkus
All 12 skills in this repoManage Deprecations
quarkusio/quarkus
Maintain @Deprecated code in the Quarkus codebase: remove code that has been deprecated for more than 12 months, add the @Deprecated annotations that were missed when a related element was…
Building And Testing
quarkusio/quarkus
How to build and test Quarkus: Maven commands, build flags, incremental builds, justfile aliases, and important build rules.
Building Docs
quarkusio/quarkus
How to build, preview, and verify Quarkus documentation locally: root Maven build, docs rebuild, Roq dev server preview.
Classloading And Runtime Dev
quarkusio/quarkus
Quarkus split classloading model, runtime-dev module wiring, conditional dependencies, and common classloading mistakes.
Converting Recorders To Services
quarkusio/quarkus
Step-by-step guide for converting Quarkus extensions from the legacy @Record/@Recorder pattern to the ServiceRegistrar service system.
Creating Extensions
quarkusio/quarkus
How to create a new Quarkus extension: full module layout, package naming, artifact naming, dependency rules, and Dev UI setup.
Related
Works with
Categories
Questions about Pull Requests
What does Pull Requests do?
Rules for preparing pull requests and commits in the Quarkus project: title conventions, description format, commit hygiene, labels, and contribution policies. Pull Requests is an agent skill from quarkusio/quarkus. Rules for preparing pull requests and commits in the Quarkus project: title conventions, description format, commit hygiene, labels, and contribution policies.
When should I use Pull Requests?
Pull Requests fits situations like: tasks that involve Pull requests.
How do I install Pull Requests in Claude Code?
Run `npx skills add quarkusio/quarkus --skill pull-requests -a claude-code`. Or copy the skill folder (.agents/skills/pull-requests in quarkusio/quarkus) into .claude/skills/pull-requests in your project. Claude Code loads it when a task matches its description.
How do I install Pull Requests in Codex?
Run `npx skills add quarkusio/quarkus --skill pull-requests -a codex`. Or copy the skill folder (.agents/skills/pull-requests in quarkusio/quarkus) into .agents/skills/pull-requests in your project. Codex loads it when a task matches its description.
Can I use Pull Requests 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 quarkusio/quarkus --skill pull-requests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pull-requests, .gemini/skills/pull-requests, .github/skills/pull-requests and .opencode/skills/pull-requests in your project.
What does Pull Requests need to run?
SKILL.md names no scripts, command-line tools or credentials: Pull Requests is instructions for the agent only.
Does Pull Requests access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Pull Requests 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 Pull Requests use?
Pull Requests 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 Pull Requests use?
About 840 tokens (SKILL.md is roughly 3.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 Pull Requests?
Skills that share tags, products or a category with Pull Requests: Creating Description For Gh PR (redis/jedis, 12k stars), Code Review Skill (awesome-skills/code-review-skill, 2.1k stars), CI Act Run (chewiebug/GCViewer, 4.6k stars) and CI Script Only Run (chewiebug/GCViewer, 4.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pull Requests?
quarkusio (a GitHub organization) maintains it in quarkusio/quarkus, which has 15,931 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 7, 2026.
Source: quarkusio/quarkus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.