writing-commits

Generate and format git commit messages using Conventional Commits standards.

7|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/borkweb/skills --skill writing-commits-borkweb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-commits
Source: https://github.com/borkweb/skills/tree/main/skills/core/writing-commits
Command: npx skills add https://github.com/borkweb/skills --skill writing-commits-borkweb

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers create clear, accurate git commit messages that help future developers understand what changed and why, streamlining the commit process and maintaining code quality.

Core Features & Use Cases

  • Commit Message Formatting: Generates commit messages following Conventional Commits standards, including type, scope, and descriptive summary.
  • Analysis of Changes: Offers commands to analyze changes in the codebase using git commands, helping users understand the intent behind code modifications.
  • Multi-Commit Suggestions: Suggests splitting changes into separate commits when dealing with multiple unrelated concerns, ensuring a well-organized commit history.
  • Output: Provides a commit message in a code block, offering the option to create the commit directly or adjust the message first.

Quick Start

Invoke the skill by asking, "write a commit message for me" or "commit this" and provide the necessary context such as the changes you've made or the files you want to commit.

Frequently Asked Questions about writing-commits

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

FAQPage Schema
How do I generate git commit messages automatically?

You can generate git commit messages automatically by asking the Skill to write a commit, which analyzes your codebase changes using git diff and formats the message according to Conventional Commits standards.

What is the best way to format conventional commits for multiple changes?

Formatting conventional commits for multiple changes is handled by suggesting you split unrelated modifications into separate commits, ensuring a well-organized commit history with accurate type, scope, and summary.

How do I write a conventional commit message from a git diff?

To write a conventional commit message from a git diff, the Skill analyzes the tracked changes, determines the commit type and scope, and outputs a formatted message in a code block for you to commit directly or adjust first.

Can I create conventional commits directly without manually typing the message?

Yes, you can create conventional commits directly, as the Skill offers an option to execute the commit automatically for you or simply provide the suggested message structure for manual review.

Do I need git installed to use this commit message generator?

Yes, you need git installed and tracking your changes, because the Skill relies on git diff commands to analyze codebase modifications and generate the conventional commit messages.

Why should I split changes into separate git commits?

You should split changes into separate git commits when dealing with multiple unrelated concerns, which ensures a well-organized commit history and helps future developers clearly understand what changed and why.