Prepare PR
Developmentprepare-prPrepare PR is an Agent Skill for development published in the QwenLM/qwen-code repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Prepare GitHub pull request title and body files from the current branch diff, especially for non-interactive CI/autofix flows that must follow the repository PR template without pushing or creating the PR.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/QwenLM/qwen-code/blob/HEAD/.qwen/skills/prepare-pr/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/prepare-pr, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Prepare PR
Create PR metadata files only. Do not push, comment, or run gh pr create.
Inputs
- Output directory: default
/tmp/autofix - Issue number: from the argument,
ISSUE, or the current branch name
Required Outputs
Write:
<output-dir>/pr-title.txt<output-dir>/pr-body.md
Workflow
- Inspect the current branch diff with
git diff origin/main...HEADand recent commit message withgit log -1 --pretty=%B. - Read
<output-dir>/e2e-report.mdif it exists. - Read
.github/pull_request_template.md. - Write a Conventional Commit style title to
pr-title.txt. - Fill the repository PR template in place and write it to
pr-body.md.
PR Body Rules
- Keep every template section heading exactly as written.
- Do not replace template headings with
Summary,Root Cause,Fix, orTests. - Use prose for motivation and changes; avoid file-by-file implementation notes unless needed for reviewer clarity.
- Include a useful Reviewer Test Plan with concrete behavior to verify.
- Fill
Evidence (Before & After)with concise before/after behavior orN/Afor non-UI changes. - Mark tested OS rows honestly. For Linux-only CI verification, mark Linux tested and macOS/Windows not tested.
- Include risk, out-of-scope, and breaking-change notes.
- Add
Fixes #<issue-number>underLinked Issueswhen an issue number is known. - Keep the
<details><summary>中文说明</summary>section and translate the English body into Chinese there. - Do not hard-wrap paragraphs or list items at a fixed column width.
Common Mistakes
- Writing a free-form PR body instead of filling the template.
- Claiming checks passed when they were not run.
- Omitting the Chinese details section.
- Using closing keywords for unrelated issues.