dev-llm-commitmsg

Draft Conventional Commits messages from staged Git changes.

3|1|Updated May 28, 2026
One-click install
npx skills add https://github.com/VMAFx/vmafx --skill dev-llm-commitmsg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-llm-commitmsg
Source: https://github.com/VMAFx/vmafx/tree/main/.claude/skills/dev-llm-commitmsg
Command: npx skills add https://github.com/VMAFx/vmafx --skill dev-llm-commitmsg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of writing a clear commit message after you have staged changes, helping you turn a diff into a reviewable Conventional Commits draft without doing the wording manually.

Core Features & Use Cases

  • Diff-aware drafting: Uses the current staged Git changes as the source of truth for the message.
  • User-controlled workflow: Presents a draft and lets you accept it, edit it in your preferred editor, or regenerate it.
  • Safety checks: Refuses unsafe branch contexts, enforces Conventional Commits format, and strips pipeline-managed attribution lines.
  • Use Case: After finishing a feature branch, ask for a commit message draft and quickly refine it before creating the commit.

Quick Start

Ask the skill to draft a Conventional Commits message from your staged changes and present it for your review.

Frequently Asked Questions about dev-llm-commitmsg

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

FAQPage Schema
How do I generate a conventional commit message from staged git changes?

The Skill inspects your current staged Git diff and drafts a Conventional Commits formatted message for your review. You can then accept, edit, or regenerate the draft before committing.

Can I use a local LLM like Ollama to draft commit messages?

Yes, Ollama provides local LLM assistance for commit drafting. The Skill keeps pre-commit review and commit message generation under your local control without relying on external services.

How does a staged diff get converted into a commit draft?

The Skill uses your staged Git changes as the source of truth, analyzing the diff to draft a Conventional Commits message. It presents the draft for you to accept, edit, or regenerate.

Does this commit message generator enforce conventional commits format validation?

Yes, the Skill enforces Conventional Commits format validation on the drafted message. It also strips Co-Authored-By and Signed-off-by lines to maintain clean attribution.

What happens if I try to generate a commit message on a protected branch?

The Skill refuses to draft a commit message on a protected branch. This safety check prevents unsafe branch contexts and protects critical branches from accidental commits.

Why are Co-Authored-By and Signed-off-by lines removed from the generated commit message?

The Skill removes Co-Authored-By and Signed-off-by lines to strip pipeline-managed attribution from the commit message. This keeps the commit history clean and attribution under user control.