git-commit-helper

Generate Spec-Kit-compliant git commit messages with Work Package references.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures git commit messages are meaningful, consistently formatted, and linked to Work Packages, enabling traceability in the dashboard.

Core Features & Use Cases

  • WP-aware messages: Prefix commits with work package IDs like [WP01], and provide structured subject/body content.
  • Automatic formatting: Conforms to Spec-Kit conventions for subject lines and commit bodies.
  • Context linking: References related WPs and shows changed files in the commit draft.

Quick Start

Ask for a commit suggestion and, after approval, run the commit: claude git-commit-helper to generate a message for your staged changes.

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 meaningful git commit messages linked to Work Packages?

Git commit messages can be generated automatically using Work Package context. The Skill reads your git status, identifies the current branch and WP context, analyzes changed files, and outputs a Spec-Kit-compliant commit message with WP prefixes like [WP01], enabling full traceability in your dashboard.

What does a properly formatted Spec-Kit git commit look like?

A Spec-Kit commit follows structured conventions: a subject line prefixed with the Work Package ID (e.g., [WP01]), a clear summary of changes, and a body that references related WPs and lists modified files. This ensures consistency across your version-control history.

Can I automate commit message creation for Spec-Driven Development workflows?

Yes. Spec-Driven Development workflows benefit from automated commit suggestions that enforce WP linkage and formatting rules. The Skill analyzes staged changes and generates drafts conforming to Spec-Kit conventions, which you approve before committing.

How do I ensure my commits stay traceable to Work Packages?

Commit messages must include WP references in a standardized format. The Skill automatically identifies related Work Packages from your branch and file context, prefixes commits with WP IDs, and surfaces those references in the message body for dashboard tracking.

What if my changes span multiple Work Packages?

The Skill identifies all related Work Packages by analyzing your branch context and changed files. It references multiple WPs in the commit body while using the primary WP in the subject prefix, maintaining full traceability across interconnected work.