vllm-pr-desc-generatorlisted

# vllm-pr-desc-generator Generate a vLLM-style PR description from code changes and save to `./outputs/`. 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 description** — write vLLM-format 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` For PRs from other repos (e.g., `vllm-project/vllm-ascend`), adjust the `--repo` flag in the fetch script accordingly. Default repo is `vllm-project/vllm`. ## Step 2: Fetch PR Data ```bash python3 /Users/shanshan-shen/.claude/skills/vllm-pr-desc-generator/scripts/fetch_pr_data.py <PR_NUMBER> \ --output /tmp/vllm_pr_<PR_NUMBER>.json ``` Optional flags: - `--token <token>` — GitHub PAT (not needed if `gh` CLI is authenticated) - `--max-diff-chars <N>` — limit diff size (default 80 000) ## Step 3: Analyze Code Changes Read `/tmp/vllm_pr_<PR_NUMBER>.json`. Focus on: - **`diff`** and **`files`**: Understand what code changed, which modules are affected - **`pr.title`**: Inf