vllm-pr-desc-generator SKILL.md skillA
vllm-pr-desc-generator from shen-shanshan/vllm-dev-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add shen-shanshan/vllm-dev-skills/vllm-pr-desc-generator@git:20261026.1de0d3dPins git:20261026.1de0d3d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- shen-shanshan/vllm-dev-skills
- Path
skills/vllm-pr-desc-generator/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261026.1de0d3d, committed Oct 26, 2026
- First version recorded
- Mar 30, 2026
- Size
- 8,318 bytes
- Repository stars
- 30
- License
- Apache-2.0
Generate a vLLM-style PR title and description (Overview / Claims / Validation / Details, following the current `.github/PULL_REQUEST_TEMPLATE.md`) from a GitHub PR's code changes. Use when the user provides a vLLM PR link or number and asks to generate, write, or draft a PR description. Triggered by requests like "帮我生成PR描述", "generate PR description for vllm PR 12345", "帮我写vllm PR的描述", "draft a PR desc for https://github.com/vllm-project/vllm/pull/12345".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# vllm-pr-desc-generator Generate a vLLM-style PR title and description from code changes and save to `./outputs/`. The format follows vLLM's current PR template ([`.github/PULL_REQUEST_TEMPLATE.md`](https://github.com/vllm-project/vllm/blob/main/.github/PULL_REQUEST_TEMPLATE.md)) and the "Pull Request Contents" section of vLLM's `pr-checklist` skill (`.agents/skills/pr-checklist/SKILL.md`). If either has changed upstream, follow the upstream version. Take `./references/example-pr-desc.md` as a style reference for the output. ## Workflow 1. **Parse PR number** — extract from URL or direct number 2. **Fetch PR data** — run `scripts/fetch_pr_data.py` 3. **Read the JSON** — load into context 4. **Analyze code changes** — understand the diff, purpose, and impact 5. **Generate PR title + description** — write vLLM-format title and description 6. **Save** — write to `./outputs/pr-<NUMBER>-desc.md` 7. **Confirm** — tell the user the output path ## Step 1: Parse PR Number Extract `<PR_NUMBER>` from user input. Accepted formats: - `https://github.com/vllm-project/vllm/pull/12345` → `12345` - `vllm PR 12345` or `PR #12345` → `12345` - Plain number `12345` → `12345` …
Read the whole file at its exact version.
How to install
mdr add shen-shanshan/vllm-dev-skills/vllm-pr-desc-generator@sha256:d01bd23fcdf6f3a1The line at the top of this page pins the label git:20261026.1de0d3d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_o45pvcuxjwjpmiau)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Mar 30, 2026 and Oct 26, 2026, about one every 210 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.1de0d3d latest | 2026-10-26 | 1de0d3d | 8,318 B | A | view · diff |
| git:20260330.d535a7e | 2026-03-30 | d535a7e | 4,619 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8318 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
shen-shanshan/vllm-dev-skills · 30 stars · license Apache-2.0 · pushed 2026-11-05 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_o45pvcuxjwjpmiau GET https://markdownregistry.com/api/v1/resolve?ref=shen-shanshan/vllm-dev-skills/vllm-pr-desc-generator GET https://markdownregistry.com/api/v1/blob/d01bd23fcdf6f3a16d999681c7db63a56e539279ce1c95fe1c472a68d777295d
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.