git-workflow

Generate conventional Git commit messages and PR summaries from diffs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kweaver-ai/kweaver-dip --skill git-workflow-kweaver-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/kweaver-ai/kweaver-dip/tree/main/studio/skills/git-workflow
Command: npx skills add https://github.com/kweaver-ai/kweaver-dip --skill git-workflow-kweaver-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate accurate and properly formatted Git commit messages, PR titles, and descriptions from code changes and diffs to improve traceability and review efficiency.

Core Features & Use Cases

  • Generate commit messages automatically from staged changes or diffs.
  • Create or rewrite PR titles and descriptions based on changes and user input.
  • Validate and enforce consistent formatting according to conventional commits standards.

Quick Start

Summarize the current changes into a concise and conventional commit message.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I generate conventional commit messages from git diffs?

To generate conventional commit messages from git diffs, the Skill analyzes staged changes and user-provided context to draft accurate summaries. It automatically formats the output according to conventional commits standards for better traceability.

Can I automatically create PR titles and descriptions from code changes?

Yes, you can automatically create PR titles and descriptions from code changes. The Skill processes branch diffs and contextual input to draft precise pull-request summaries, and it can also rewrite existing messages to improve review efficiency.

What is the best way to rewrite existing pull-request messages?

The best way to rewrite existing pull-request messages is to provide the current text alongside the code diff. The Skill evaluates the changes and user input to validate and enforce consistent formatting according to conventional commits standards.

Do I need staged changes to generate a git commit message?

You do not strictly need staged changes to generate a git commit message. The Skill can process general diffs, user-provided context across repositories and branches, and staged changes to produce accurate summaries.

How does conventional commit validation work for staged changes?

Conventional commit validation for staged changes works by analyzing the diff and formatting the generated message to meet standard guidelines. The Skill enforces consistent formatting to ensure commit history traceability and improves code review efficiency.