b2b-web-create-commit

Generate type-based Git commits from analyzed code changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/herren-official/product-agents --skill b2b-web-create-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: b2b-web-create-commit
Source: https://github.com/herren-official/product-agents/tree/main/skills/b2b-web/create-commit
Command: npx skills add https://github.com/herren-official/product-agents --skill b2b-web-create-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically analyze changes in the working directory and generate commits that conform to the project's commit rules, reducing manual planning and human error.

Core Features & Use Cases

  • Analyze changed files and categorize edits (docs, tests, features, fixes)
  • Extract IDs from branch names (e.g., GBIZ-XXXXX) to link commits to work items
  • Split changes into separate commits by type (feat, fix, docs, style) and auto-generate messages

Quick Start

Run /create-commit to automatically generate commits based on the analyzed changes.

Frequently Asked Questions about b2b-web-create-commit

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

FAQPage Schema
How do I automatically generate git commits that follow project conventions?

To automate commit generation, you can run the /create-commit command to analyze working directory changes, classify edits by type, and auto-generate convention-compliant commit messages.

How do I link my git commits to a work item ID from the branch name?

Linking commits to work items involves extracting IDs, such as GBIZ-XXXXX, directly from the branch name and injecting them into the auto-generated commit messages for traceability.

Can I split multiple file changes into separate commits based on type?

Splitting changes into separate commits is supported by analyzing changed files, categorizing edits into types like feat, fix, docs, or style, and generating individual commits for each category.

How does automated commit generation validate against commit rules?

Automated commit validation works by checking the generated message against the central commit-convention documentation and executing git operations only after the message passes the validation.

What is the best way to reduce manual planning and errors when committing code changes?

Reducing manual planning and errors is achieved by automatically detecting code changes, classifying commit types, generating structured messages, and validating them against project rules before execution.