dev-commit-writer

Generate style-consistent commit messages from staged and unstaged code changes.

5|Updated Apr 29, 2026

Search Tags:#automation #git #version control #code changes #commit message

Ready to run

npx skills add https://github.com/Jason-chen-coder/dev-skills --skill dev-commit-writer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-commit-writer
Source: https://github.com/Jason-chen-coder/dev-skills/tree/main/skills/dev-commit-writer
Command: npx skills add https://github.com/Jason-chen-coder/dev-skills --skill dev-commit-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers craft accurate and style-consistent commit messages based on current code changes, ensuring clear project history documentation.

Core Features & Use Cases

Automatic Message Generation: Creates commit messages in the style of existing history or conventions.
Scope and Incidental Changes Analysis: Detects unrelated modifications and suggests splitting into multiple commits.
Use Case: When preparing a feature branch, a user can ask this Skill to produce a concise commit message that accurately reflects recent code changes, streamlining the commit process.

Quick Start

Ask the AI to generate a commit message for your current uncommitted changes, optionally specifying staged files or a particular path.

Frequently Asked Questions about dev-commit-writer

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

FAQPage Schema

How do I generate a commit message for staged and unstaged code changes?▼

To generate a commit message for code changes, analyze current unstaged and staged modifications to produce a clear, style-consistent summary. This process detects unrelated modifications and suggests splitting them into multiple commits for accurate version control history.

How does commit message generation match my repository's existing style?▼

Commit message generation matches repository style by analyzing existing commit history and conventions. It uses your past formatting patterns to produce style-consistent messages that integrate seamlessly with your current project documentation standards.

Can I generate a commit message for a specific file path or staged files?▼

Yes, you can generate a commit message for specific staged files or a particular path. By optionally specifying the target files, the message generation focuses solely on those code changes to provide an accurate and concise summary.

How do I handle unrelated modifications when preparing a feature branch commit?▼

To handle unrelated modifications when preparing a commit, the generation process analyzes scope and detects incidental changes. It suggests splitting unrelated code changes into multiple separate commits to maintain clear project history documentation.

What's the best way to automate git commit messages for self-reviewed changes?▼

The best way to automate git commit messages for self-reviewed changes is generating them from current code modifications. This ensures style-consistent documentation by analyzing staged and unstaged differences while detecting unrelated modifications for splitting.