git-workflow

Enforce conventional commit messages and branch naming rules during Git commits.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/mesca/claude-plugins --skill git-workflow-mesca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/mesca/claude-plugins/tree/main/plugins/wf/skills/git-workflow
Command: npx skills add https://github.com/mesca/claude-plugins --skill git-workflow-mesca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains a clean, navigable Git history by enforcing consistent commit messages and standardized branching strategies across teams.

Core Features & Use Cases

  • Pre-commit checks: run lint, format, type checks, and tests before every commit.
  • Commit message format: enforce conventional types (feat, fix, docs, style, refactor, test, perf, chore, ci) and subject/body/footer guidelines.
  • Branch naming: recommended patterns like feature/description, fix/description, and chore/description to improve traceability.
  • Security and quality: ensure sensitive data isn't committed and verify that changes meet established development standards.

Quick Start

Configure your repository to enforce the predefined pre-commit checks and follow the commit message and branch naming conventions.

Frequently Asked Questions about git-workflow

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

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

You can enforce conventional commit messages by applying rules for types like feat, fix, docs, and chore during Git commits. This Skill validates commit message formats, subject lines, and footers to maintain a clean, navigable project history.

What is the best way to standardize branch naming for feature and fix workflows?

Standardizing branch naming involves applying consistent patterns like feature/description, fix/description, and chore/description. This Skill enforces these Git branching rules to improve traceability and maintain a structured, navigable project history across software teams.

How do pre-commit checks improve code quality before a Git commit?

Pre-commit checks improve code quality by running lint, format, type checks, and tests before every Git commit is finalized. This Skill enforces these automated quality gates to ensure changes meet established development standards and prevent broken code from entering the repository.

Can I run a security checklist during Git branching activities to prevent sensitive data commits?

Yes, you can run a security checklist during Git branching and commits to ensure sensitive data isn't committed. This Skill enforces security checks alongside conventional commit types and branch naming rules to verify changes meet established development standards.

Do I need any dependencies to configure automated pre-commit checks for my repository?

No dependencies are required to configure automated pre-commit checks for your repository. This Skill operates independently to enforce lint, format, type checks, and tests before every Git commit without relying on external modules or component libraries.