create-commit

Generate conventional commit messages from staged Git changes.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/lorrandavid/.dotfiles --skill create-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-commit
Source: https://github.com/lorrandavid/.dotfiles/tree/main/.config/.copilot/skills/create-commit
Command: npx skills add https://github.com/lorrandavid/.dotfiles --skill create-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating clear, standards-compliant commit messages that follow the conventional commits style, reducing guesswork and improving project history readability.

Core Features & Use Cases

  • Analyze the staged changes to understand what was modified and categorize it.
  • Suggest commit type (feat, fix, docs, style, refactor, test, chore) and an optional scope based on the changes and branch naming conventions.
  • Format a conventional commit message with an title and optional scope, plus a concise body when needed.
  • Provide prompts when information is ambiguous to ensure the final message is accurate.

Quick Start

Provide a conventional commit message for the currently staged changes.

Frequently Asked Questions about create-commit

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

FAQPage Schema
How do I generate conventional commit messages from staged changes?

You can generate conventional commit messages by analyzing your staged changes via git diff --cached --name-only. The tool categorizes modifications and formats a compliant commit title and body with the appropriate type and optional scope.

What is the best way to automatically format a git commit message for a bugfix or feature?

Automatically formatting a git commit message involves analyzing the staged files to select a suitable type like feat, fix, or docs. The tool then structures a conventional commit title and concise body based on the detected changes.

How does conventional commit type and scope selection work for version control?

Conventional commit type and scope selection works by evaluating the modified files in your staged changes and branch naming conventions. It suggests types like fix or refactor and applies an optional scope to ensure history readability.

Can I use this to generate commit messages across different types of code updates?

Yes, you can use this to generate commit messages across typical Git workflows. It applies to feature, bugfix, and docs updates, guiding type and scope decisions to ensure compliance with conventional commits standards.

What happens when the staged changes are ambiguous for commit message generation?

When staged changes are ambiguous for commit message generation, the tool provides prompts to request clarification. This ensures the final commit title and body accurately reflect the modifications before formatting.