git-commit-helper

Format and validate Git commit messages using Conventional Commits.

14|2|Updated Nov 12, 2025
One-click install
npx skills add https://github.com/tbartel74/Vigil-Code --skill git-commit-helper-tbartel74
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit-helper
Source: https://github.com/tbartel74/Vigil-Code/tree/main/.claude/skills/git-commit-helper
Command: npx skills add https://github.com/tbartel74/Vigil-Code --skill git-commit-helper-tbartel74

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated git workflow management for Vigil Guard v2.0.0, including Conventional Commits, CHANGELOG generation, commit validation, pre-commit hooks, and release versioning.

Core Features & Use Cases

  • Commit Message Guidance: Enforce conventional commits format and avoid AI attribution.
  • CHANGELOG & Versioning: Generate changelogs and manage semantic releases.
  • Pre-commit Hooks: Validate commits before they are created.

Quick Start

Use the smart-commit script to generate and format messages, install pre-commit hooks, and run commit validation.

Frequently Asked Questions about git-commit-helper

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

FAQPage Schema
How do I enforce conventional commits in my Git workflow?

Conventional commits enforce a standardized format—<type>(<scope>): <subject>—for all commit messages. This Skill automates that enforcement through pre-commit hooks and validation, ensuring consistency across feature branches, bug fixes, and documentation changes while blocking AI-attributed commits.

Can I generate a CHANGELOG automatically from my commits?

Yes. This Skill parses conventional commit messages to auto-generate changelogs and manage semantic versioning. It extracts commit types (feat, fix, docs, etc.) and scopes to build structured release notes tied to version increments.

What types of commits does this support?

The Skill recognizes and validates ten commit types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, and revert. Each type maps to semantic versioning rules and changelog organization.

How do pre-commit hooks validate my messages before they're created?

Pre-commit hooks intercept commits before they're written to the repository, checking message format against conventional commit rules. If a message fails validation, the commit is rejected and you're prompted to correct the type and subject.

Does this work with existing Git workflows and CI/CD pipelines?

Yes. The Skill integrates with automated tooling for linting, testing, and changelog automation. It's designed for development pipelines and works across feature branches, maintenance tasks, and release versioning without requiring workflow restructuring.

What happens if I don't provide a commit type or subject?

The Skill prompts you interactively to supply the missing type and subject before allowing the commit to proceed, ensuring no commit bypasses the conventional format.