git-commit

Generate Angular-format conventional commit messages from user prompts.

69|9|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/Tibsfox/gsd-skill-creator --skill git-commit-tibsfox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/Tibsfox/gsd-skill-creator/tree/main/examples/skills/git-commit
Command: npx skills add https://github.com/Tibsfox/gsd-skill-creator --skill git-commit-tibsfox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating conventional commit messages can be repetitive and error-prone. This skill ensures messages follow a consistent Angular-style format so your git history is clear and machine-readable.

Core Features & Use Cases

  • Generate properly structured commit messages from user prompts, including type, scope, and subject.
  • Validate and standardize messages to conform to the Conventional Commits specification for predictable changelogs.
  • Use in automation to suggest commits during code changes or CI pipelines.

Quick Start

Provide a conventional commit message for the current changes using the Angular format.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate conventional commit messages for git automatically?

To generate conventional commit messages, this skill analyzes your prompts and applies the Angular format structure of type, optional scope, and subject to produce consistent, readable git history.

What is the Angular format for conventional commits?

The Angular format for conventional commits structures messages as type(scope): subject, optionally followed by a body and footer for references or breaking changes, ensuring your version history remains clear and machine-readable.

Can I use conventional commits across projects of varying sizes and languages?

Yes, conventional commits apply to any codebase using git across projects of varying sizes and languages, standardizing your commit messages for predictable changelogs regardless of the technical stack.

How do I validate git commit messages against the Conventional Commits specification?

Validating git commit messages involves checking that they conform to the Conventional Commits specification, which this skill enforces by standardizing prompts into the required type, scope, and subject structure.

Does this conventional commit generator work in CI pipelines?

Yes, you can use this conventional commit generator in CI pipelines and automation to suggest properly structured commit messages during code changes, maintaining consistent and machine-readable version history.