git-commit-helper

Generate Spec-Kit commit messages with Work Package links from git status.

1|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/dan1901/spec-mix --skill git-commit-helper-dan1901
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-helper
Source: https://github.com/dan1901/spec-mix/tree/main/.claude/skills/git-commit-helper
Command: npx skills add https://github.com/dan1901/spec-mix --skill git-commit-helper-dan1901

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically generates well-structured commit messages that follow Spec-Kit conventions and link commits to Work Packages, ensuring consistent version control and traceability.

Core Features & Use Cases

  • WP-aware commits: Detects the related Work Package from branch or recent changes.
  • Conventional messages: Enforces subject/body style and includes related WP IDs.
  • Proposal & optional execution: Presents a ready-to-run commit message and can execute the commit when requested.

Quick Start

Ask Claude to generate a commit message for your current changes, linked to the relevant Work Package (e.g., WP01), then stage and commit using the generated message.

Frequently Asked Questions about git-commit-helper

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

FAQPage Schema
How do I generate commit messages that link to work packages?▼

Git commit message generation automatically detects your current Work Package from branch names or recent changes, then produces a formatted commit message with an imperative subject, optional body, and modified files list aligned with Spec-Kit conventions, ready to execute or review.

What are Spec-Kit commit conventions and why use them?▼

Spec-Kit conventions enforce consistent commit message structure—imperative subject line, detailed body, and Work Package linkage—ensuring traceability across version control and enabling automated tracking of changes to specific tasks in Spec-Driven Development workflows.

Can I automate commit message creation during my git workflow?▼

Yes, commit message automation inspects your git status and staged changes, identifies the relevant Work Package context, and proposes a complete, ready-to-run commit command that follows Spec-Kit format without manual composition.

How does the Skill identify which Work Package a commit belongs to?▼

The Skill determines Work Package association by parsing branch names for WP identifiers and examining recent changes against your Spec-Driven Development context, then embeds the linked WP ID in the generated commit message.

Does this work with existing git repositories and branch naming?▼

Yes, the Skill operates on any git repository during commit drafting by reading current branch state and work package context; it generates proposals without requiring special repository setup, making it compatible with standard git workflows.

What if my commit touches multiple work packages or files?▼

The generated commit message includes a comprehensive list of all modified files and can link to the primary Work Package from your branch or context; you review the proposal before execution and can adjust if needed.