Skip to content
cccskills
FreePublished on GitHub

prepare-pr

Prepare pull request title and body files from the current branch diff and available test reports. Follow the repository template, include concrete reviewer checks, and provide an English body with a Chinese translation.

OriginalShow the original description

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.

Works withGitHub
See how to install

Good for

  • Draft a pull request from current branch changes
  • Prepare PR metadata files for CI or autofix
  • Document reviewer checks and tested operating systems
  • Prepare English and Chinese pull request descriptions

Files included (1)

  • SKILL.md2.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

agent-delegation

FreeSummary

Write clear briefs for subagents and conversation forks, agents that inherit conversation history. Specify purpose, known findings, scope, and expected output while respecting each agent's existing role and separating research requests from implementation.

  • Writing a focused research brief for a subagent
  • Specifying files and constraints for implementation
  • Defining scope for an agent inheriting conversation history
QwenLM/qwen-code28.6KUpdated Oct 19, 2026

Compare a feature implemented in Qwen Code with Codex or Claude Code under the same scenario. Capture communication and terminal records, inspect tool definitions and outputs, and guide fixes toward matching observable behavior.

  • Checking a reproduced feature against its reference agent
  • Comparing tool definitions and required arguments
  • Investigating differences in terminal output
QwenLM/qwen-code28.6KUpdated Oct 19, 2026

Reproduce a Codex or Claude Code feature in Qwen Code or another command-line agent. Capture requests, terminal output, and state changes, then use that evidence to implement focused behavior and add a verification path.

  • Reproduce an existing agent's slash command
  • Inspect request formats and tool definitions
  • Compare terminal output and saved state
QwenLM/qwen-code28.6KUpdated Oct 19, 2026

autofix

FreeSummary

Review local uncommitted changes, verify findings, and repeat focused repairs until the review converges or a blocker remains. Also supports Qwen Code issue fixes and review responses within workflows run through GitHub Actions.

  • Review and repair local uncommitted changes
  • Develop a focused fix for a selected issue
  • Verify and address pull request feedback
QwenLM/qwen-code28.6KUpdated Oct 19, 2026

batch

FreeSummary

Apply the same operation across multiple files using parallel worker agents. The skill finds matching files, divides the work, and reports successes, failures, and skipped files, with a preview option before edits.

  • Add license headers across source files
  • Convert JavaScript files to TypeScript
  • Fix the same lint issue in multiple files
QwenLM/qwen-code28.6KUpdated Oct 19, 2026

batch-api

FreeSummary

Prepare shared instructions for translating, rewriting, or extracting information from many independent files, then submit a plan through the DashScope Batch API. Processing runs asynchronously at half the realtime list price and delivers new files later.

  • Translate many documents using shared terminology
  • Rewrite independent files into a consistent format
  • Extract structured data from a collection of files
QwenLM/qwen-code28.6KUpdated Oct 19, 2026

See all skills by QwenLM

Report a problem with this skill