conventional-committer

Generate and apply Git commits matching the project's commit style.

2|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/akaihola/skills-akaihola --skill conventional-committer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conventional-committer
Source: https://github.com/akaihola/skills-akaihola/tree/main/conventional-committer
Command: npx skills add https://github.com/akaihola/skills-akaihola --skill conventional-committer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates the creation of Git commits that reflect recent history and current changes, ensuring consistent, well-formed messages.

Core Features & Use Cases

  • Analyzes recent commits to infer project style and generate message subject lines.
  • Stages relevant changes when needed (based on user instruction) and commits them with a matching message.
  • Reads the current staged diff to describe what changed and preserves safety checks to avoid empty commits.
  • Supports multi-chunk context retrieval via the git_context_chunks.py helper for large diffs.

Quick Start

Ask to commit the current changes, and the skill will gather Git context and create a conventional commit message before applying it.

Frequently Asked Questions about conventional-committer

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

FAQPage Schema
How do I automate generating git commit messages from staged changes?

This skill automates generating git commits by analyzing your recent history and staged diff. It infers your project's commit style, produces a matching message, and reports the resulting commit hash after applying it.

Can I create a git commit that automatically matches my repository's history style?

Yes, you can create a commit that matches your repository's history style because the skill validates generated messages against recent commits. It reads prior history to infer subject line formatting and applies that exact convention to your new commit.

How does this approach handle large staged diffs when creating a commit?

To handle large staged diffs when creating a commit, the skill uses a helper script to retrieve context in chunks. This multi-chunk context retrieval ensures the entire diff is processed accurately without exceeding processing limits.

Do I need to manually stage files before asking it to create a commit?

You do not always need to manually stage files before creating a commit. Based on your instructions, the skill can stage relevant changes automatically before analyzing the diff, generating the message, and applying the commit with built-in safety checks.

Why does the automated commit process include safety checks for empty commits?

The automated commit process includes safety checks for empty commits to prevent cluttering your git history. It validates the staged diff content before applying the generated message, ensuring only meaningful changes are recorded.