prepare-pr
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.
git clone --depth 1 https://github.com/QwenLM/qwen-code /tmp/prepare-pr && cp -r /tmp/prepare-pr/.qwen/skills/prepare-pr ~/.claude/skills/prepare-prSKILL.md
# 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 1. Inspect the current branch diff with `git diff origin/main...HEAD` and recent commit message with `git log -1 --pretty=%B`. 2. Read `<output-dir>/e2e-report.md` if it exists. 3. Read `.github/pull_request_template.md`. 4. Write a Conventional Commit style title to `pr-title.txt`. 5. 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`, or `Tests`. - 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 or `N/A` for 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>` under `Linked Issues` when 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.
Use after a Codex or Claude Code feature has been implemented in Qwen Code to run the selected reference agent and Qwen Code under the same scenario, capture HTTP and terminal traces, compare request bodies, tool/function schemas, outputs, and iterate until the reproduced behavior is close enough.
Use when reproducing an existing Codex or Claude Code feature in Qwen Code or another agent CLI by choosing a reference agent, capturing HTTP request bodies, prompts, tool/function schemas, terminal output, and then implementing the matching behavior in the target repo.
Review and repair current local changes until they converge, or run Qwen Code Autofix issue and review workflows from GitHub Actions.
Fix a bug from a GitHub issue, following the reproduce-first
Classify a bounded batch of stale PR CI failures and choose the safest response.
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection, auto-merge candidates, labeling). Also covers creating, inspecting, and repairing a CodeScope index. Use for: code structure, who calls what, why something changed, similar functions, module boundaries, bug tracing, class relationships, PR risk/conflicts, or any question benefiting from a code knowledge graph. Applies when a `.codegraph` index exists in the workspace, or when the user wants to create one.
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
Stabilize a flaky test with a minimal, assertion-preserving fix — never by weakening or deleting the check.