dbx-work-commit-pr

Name: dbx-work-commit-pr
Availability: InStock
Author: DBvc

Convert final changesets into Chinese commit messages and contract-style PR descriptions.

5|1|Updated Jan 18, 2026

Search Tags:#workflow #commit #review #chinese #contract #pull-request #proof

Ready to run

npx skills add https://github.com/DBvc/skills --skill dbx-work-commit-pr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dbx-work-commit-pr
Source: https://github.com/DBvc/skills/tree/main/skills/dbx-work-commit-pr
Command: npx skills add https://github.com/DBvc/skills --skill dbx-work-commit-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

在软件开发工作流中，自动将最终变更集转换为中文的 commit message 和合同式 PR 描述，帮助团队以一致、可审计的方式记录变更。

Core Features & Use Cases

基于最终变更的输出：仅以最终变更集为事实边界，生成可追溯的提交与 PR 内容。
合同式四块 PR 结构：包含做了什么/为什么、证明它可行、风险与 AI 参与、评审关注点等四部分。
工作场景适用性：适用于中文工作场景的内部协作、代码变更记录、审计与回溯需求。

Quick Start

输入最终变更集，系统将输出以 M-xxx(type): 标题的中文 commit 和包含 Proof、Risk、Review focus 的 PR 描述。

Frequently Asked Questions about dbx-work-commit-pr

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

FAQPage Schema

How do I generate Chinese commit messages and PR descriptions from a changeset?▼

Contract-style PR descriptions structure changes into four sections: what was done and why, proof it works, risks and AI involvement, and review focus points, ensuring consistent and auditable code change records.

Can I use staged changes or working-tree changes to generate the PR description?▼

Only the final changeset is used as the factual boundary. It avoids including chat history, failed attempts, or temporary debugging, ensuring the generated commit message and PR description reflect the actual code changes.

What is the best way to structure a PR for Chinese internal collaboration and auditing?▼

It is suited for Chinese work scenarios requiring contract-style PRs with structured sections. It applies to internal collaboration, code change recording, and audit traceability needs where a formal PR structure is required.

Why does the generated PR exclude my chat history and failed debugging attempts?▼

The generated PR excludes chat history and failed attempts because the system uses only the final changeset as the factual boundary. This prevents temporary debugging or failed tries from polluting the auditable commit and PR records.