git-workflow

Name: git-workflow
Availability: InStock
Author: eysenfalk

Enforce Git branch naming, commit message formats, and merge policies.

Updated Feb 10, 2026

Search Tags:#git #workflow #code review #security #commit #branching #merge

Ready to run

npx skills add https://github.com/eysenfalk/git-review --skill git-workflow-eysenfalk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/eysenfalk/git-review/tree/main/.claude/skills/git-workflow
Command: npx skills add https://github.com/eysenfalk/git-review --skill git-workflow-eysenfalk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enforces a consistent and secure Git workflow, preventing common errors and ensuring code quality through automated checks and clear guidelines.

Core Features & Use Cases

Branch Naming Enforcement: Ensures branches follow a strict <type>/<ticket-id>-<description> format.
Commit Message Formatting: Guides users to create descriptive commit messages that include ticket references.
Merge Policy Adherence: Prevents direct commits to main and enforces review gates before merging.
Use Case: When creating a new feature branch, the skill ensures it's named correctly and prompts for a ticket ID, preventing non-compliant branches from being created.

Quick Start

Follow the git-workflow skill's guidelines for creating branches, committing code, and merging pull requests.

Frequently Asked Questions about git-workflow

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

FAQPage Schema

How do I enforce git branch naming conventions automatically?▼

To enforce git branch naming conventions, this Skill validates that branches follow a strict <type>/<ticket-id>-<description> format. It prompts for a ticket ID during branch creation, preventing non-compliant branches from being created.

How do I format commit messages to include ticket references?▼

Formatting commit messages with ticket references is handled by guiding users to create descriptive commit messages. The Skill enforces commit message formats during pre-commit validation to ensure ticket adherence before commits are finalized.

How do I prevent direct commits to the main branch?▼

To prevent direct commits to the main branch, this Skill enforces merge policy adherence and review gates. It utilizes pre-commit hooks to manage review status and block unauthorized commits before merges occur.

What are pre-commit hooks used for in a secure git workflow?▼

Pre-commit hooks in a secure git workflow provide automated validation of ticket adherence, branch naming, and review status. They enforce security rules and workflow guidelines before commits and merges are executed.

Can I enforce code review gates before merging code?▼

Yes, you can enforce code review gates before merging code. This Skill manages review gate enforcement and security rules, ensuring that review status is validated before any merge is permitted.

How do I ensure consistent git workflow practices across my team?▼

To ensure consistent git workflow practices, this Skill automates checks for branch naming, commit message formatting, and merge policies. It prevents common errors and maintains code quality through clear guidelines and pre-commit validation.