commit-writer

Generate conventional git commit messages from staged diffs and repository history.

7|Updated Oct 20, 2025

Search Tags:#automation #git #commit #history #diff #messages #conventional-commits

Ready to run

npx skills add https://github.com/borkweb/bork-ai --skill commit-writer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-writer
Source: https://github.com/borkweb/bork-ai/tree/main/skills/commit-writer
Command: npx skills add https://github.com/borkweb/bork-ai --skill commit-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of clear, meaningful git commit messages by analyzing git status, diffs, and repository history, ensuring messages follow Conventional Commits and align with project conventions, saving you time and reducing miscommunication.

Core Features & Use Cases

Context-aware: Analyzes staged changes, diffs, and history to propose precise messages.
Conventional Commits Compliance: Defaults to the Conventional Commits specification and suggests types like feat, fix, docs, etc.
Repo Style Adaptation: Aligns with the repository's existing commit message style for consistency.
Use Case: Ideal for daily commits to improve traceability and readability.

Quick Start

Use the commit-writer skill to generate a commit message for the current staged changes.

Frequently Asked Questions about commit-writer

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

FAQPage Schema

How do I generate conventional commit messages automatically?▼

Conventional commit messages are generated by analyzing your staged git changes and diffs, then applying the Conventional Commits specification to produce a message with the correct type (feat, fix, docs, etc.), a concise subject line, and a descriptive body explaining what changed and why.

Can commit-writer adapt to my repository's existing commit style?▼

Yes. The Skill analyzes your repository's git history and existing conventions, then aligns generated messages with your project's established patterns for consistency across the codebase.

What's the best way to write clear, traceable commit messages?▼

Clear commits follow Conventional Commits with a 50-character subject line and a body explaining the change's purpose. This Skill automates that process by extracting context from staged diffs and repository history to create atomic, meaningful messages.

Does this work with large diffs or complex staging scenarios?▼

The Skill generates messages for current staged changes by analyzing git status and diffs. For complex scenarios, ensure changes are logically staged as atomic commits; the message will reflect the staged content and align with Conventional Commits conventions.

Why do commit messages matter for git history?▼

Standardized, descriptive commit messages improve traceability, enable automated changelog generation, and help teams understand change intent. This Skill enforces Conventional Commits to reduce miscommunication and maintain readable history.

Can I use commit-writer to enforce team commit standards?▼

The Skill generates messages compliant with Conventional Commits and your repository's style conventions, ensuring consistency. Combined with repository practices, it helps teams maintain uniform, high-quality commit history.