skills.rest
mezivillager
mezivillagerCOMMUNITY
Explore all skills by this author →
GitHub

git-operations

Validate Git commit messages against Conventional Commits and branch rules.

1|Updated Mar 3, 2026
Search Tags:#git#versioning#commit#conventional commits#branching#semantic release
One-click install
npx skills add https://github.com/mezivillager/hacer --skill git-operations-mezivillager
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-operations
Source: https://github.com/mezivillager/hacer/tree/main/.claude/skills/git-operations
Command: npx skills add https://github.com/mezivillager/hacer --skill git-operations-mezivillager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that all Git commits adhere to the Conventional Commits specification, which is crucial for automated changelog generation and semantic versioning.

Core Features & Use Cases

  • Commit Message Formatting: Guides users to create commit messages that follow the <type>[optional scope]: <description> format.
  • Branch Validation: Helps maintain a clean and consistent branch state before committing.
  • Use Case: Before merging a feature branch, use this skill to ensure all commits are properly formatted, preventing issues with automated release pipelines.

Quick Start

Run this skill to format your commit messages correctly and validate your branch state.

Frequently Asked Questions about git-operations

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

FAQPage Schema
How do I enforce conventional commits for automated semantic release?▼

Enforce conventional commits by validating commit messages against semantic-release requirements, ensuring adherence to specific commit types like feat, fix, and docs. This enables automated changelog generation and semantic versioning.

What is the correct format for a conventional commit message?▼

The correct conventional commit message format is <type>[optional scope]: <description>. You must use specific commit types such as feat or fix, and you can denote breaking changes with an exclamation mark.

How do I validate branch state before merging a feature branch?▼

Validate branch state before merging by enforcing branch lifecycle rules to ensure branch state integrity. This maintains a clean and consistent branch state, preventing issues with automated release pipelines.

Do I need to specify a scope for every conventional commit?▼

No, specifying a scope is optional for conventional commits. Commit messages follow the <type>[optional scope]: <description> format, meaning you can omit the scope and still meet semantic-release validation requirements.

How do I indicate a breaking change in a semantic release commit?▼

Indicate a breaking change in a semantic release commit by appending an exclamation mark. This notation ensures the commit is properly recognized during automated versioning and changelog generation.

Why are my automated release pipelines failing during branch merges?▼

Automated release pipelines fail during branch merges when commit messages lack proper conventional commit formatting. Validating commits against semantic-release requirements and ensuring branch state integrity prevents these pipeline issues.

Related Skills

Explore More Software Engineering Skills→
ian-pascoeian-pascoe
1

git-commit

Generate conventional git commit messages and stage related file changes.

Community
Advanced
kurokeitakurokeita
1

changelog-automation

Automate changelog generation from commits, PRs, and releases.

Community
Intermediate
sunLeeesunLeee

check-commit-message

Validate Git commit messages against Conventional Commits rules.

Community
Intermediate
vanman2024vanman2024
3

Git Workflows

Standardize git workflows with commit templates, branch helpers, and hook scripts.

Community
Basic