dbx-open-source-commit-pr

Generate open-source commit messages and PR descriptions from final diffs.

5|1|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/DBvc/skills --skill dbx-open-source-commit-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dbx-open-source-commit-pr
Source: https://github.com/DBvc/skills/tree/main/skills/dbx-open-source-commit-pr
Command: npx skills add https://github.com/DBvc/skills --skill dbx-open-source-commit-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Drafting clean, public-facing commit messages and PR descriptions from final diffs and commits, reducing ambiguity and speeding up OSS collaboration.

Core Features & Use Cases

  • Generate or rewrite concise English commit messages for OSS from final changesets, staged changes, or specific commits; create corresponding PR descriptions for public repositories.
  • Review and refine PR bodies to align with open-source contribution standards.
  • Enforce guidance for validation wording and public-state disclosure, while excluding internal or contract-level details.

Quick Start

Provide the final diff or target commit, and I will return a concise OSS commit message and a PR description ready for public sharing.

Frequently Asked Questions about dbx-open-source-commit-pr

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

FAQPage Schema
How do I generate a commit message from a staged diff for an open-source repository?▼

Generate a commit message from a staged diff by providing the changeset to translate it into a concise, public-facing English commit message aligned with the repository's style guidelines.

How do I write a PR description for a public repository from final commits?▼

Write a PR description for a public repository by applying the final commit changeset to produce a polished PR body that enforces public-facing language and excludes internal or contractual details.

Can I use a specific commit to rewrite an OSS commit message?▼

You can use a specific commit to rewrite an OSS commit message by supplying the target commit, which refines the output to align with open-source contribution standards and validation guidance.

What is the best way to ensure my PR body excludes internal details?▼

The best way to ensure your PR body excludes internal details is to apply open-source contribution standards during generation, enforcing public-state disclosure while stripping out contract-level or proprietary information.

Does this commit message generator work with final changesets and staged changes?▼

This commit message generator works with final changesets, staged changes, and specific commits, translating the provided diffs into polished open-source commit messages and PR descriptions.

Why should I avoid internal or contractual details in open-source PR descriptions?▼

You should avoid internal or contractual details in open-source PR descriptions to enforce public-facing language, ensure appropriate public-state disclosure, and align with open-source contribution standards.