chinese-git-delivery

Generates Chinese commit messages, PR details, and delivery reports for Git workflows.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/DJackyB/Project_Rent --skill chinese-git-delivery-djackyb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chinese-git-delivery
Source: https://github.com/DJackyB/Project_Rent/tree/main/.claude/skills/chinese-git-delivery
Command: npx skills add https://github.com/DJackyB/Project_Rent --skill chinese-git-delivery-djackyb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When committing, pushing, or creating pull requests, developers often ship code without clear titles, descriptions, verification notes, or risk statements. This Skill standardizes Git delivery by producing complete Chinese-language commit messages, PR details, and delivery summaries so nothing is left undocumented. ## Core Features & Use Cases - Scoped Staging Review: Checks branch, working tree status, and untracked files to separate deliverable changes from unrelated leftovers before committing. - Chinese Commit & PR Content: Generates Chinese titles with conventional prefixes (feat:, fix:, refactor:, docs:, chore:) plus bodies covering what changed, why, verification status, and remaining risks. - Branch Strategy Guardrails: Avoids pushing directly to main unless explicitly requested, preferring a dedicated branch before creating a PR. - Use Case: After finishing a feature, ask the assistant to commit and open a PR; it will stage only relevant files, write a Chinese commit message and PR description with verification and risk notes, and report the branch, SHA, and PR result. ## Quick Start Use the chinese-git-delivery skill to commit my current changes, push them to a new branch, and open a PR with a full Chinese title and description.

Frequently Asked Questions about chinese-git-delivery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a good Chinese commit message for Git?▼

Use a short Chinese title with a conventional prefix like feat:, fix:, refactor:, docs:, or chore:, followed by a body covering what changed, why, verification status, and remaining risks. State facts plainly and explicitly note if tests were not run.

How to create a pull request with a complete Chinese description?▼

Push your changes to a dedicated branch first, then create the PR with a Chinese title and a body covering background, the changes made, verification results, risks and caveats, and follow-up suggestions if any exist.

Should I push directly to the main branch?▼

Only push directly to main when the user explicitly requests it. Otherwise, create a separate branch, push there, and open a pull request so changes can be reviewed before merging.

What should a Git delivery report include after pushing?▼

A delivery report should state the commit title, commit SHA, target branch, whether a PR was created, and which files were intentionally excluded. It must also disclose if tests were not run or push/PR steps could not complete.

How do I avoid committing unrelated untracked files in Git?▼

Review git status before staging and separate deliverable changes from leftover artifacts like caches, temp directories, or other threads' output. Stage only the files belonging to the current delivery scope.