git-workflow-skill

Name: git-workflow-skill
Availability: InStock
Author: mthang1801

Enforce Git workflow rules for branch naming, Conventional Commits, and PR/MR creation.

Updated Aug 23, 2026

Search Tags:#git #workflow #branching #pull-request #conventional-commits #branch-naming #feature-branch

Ready to run

npx skills add https://github.com/mthang1801/go-domain-driven-design --skill git-workflow-skill-mthang1801

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflow-skill
Source: https://github.com/mthang1801/go-domain-driven-design/tree/main/.claude/skills/git-workflow-skill
Command: npx skills add https://github.com/mthang1801/go-domain-driven-design --skill git-workflow-skill-mthang1801

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git workflow, branching strategy, and Conventional Commits guidance for Data Visualizer. Use this skill whenever the user needs to create a branch, prepare a commit, name a branch, write a commit message, sync with develop, open a PR/MR, or validate repo workflow rules, even if they only ask loosely about Git.

Core Features & Use Cases

Enforces Conventional Commits across the codebase to maintain a clean, scannable history.
Defines and validates branch naming conventions (e.g., feature/, bugfix/, chore/) to prevent direct pushes to develop.
Guides safe branching operations: checkout, create, and rebase with develop before PRs/MRs.
Supports optional Jira integration to link branches with tasks when jira-skill is available.

Quick Start

Create a feature branch using the type/short-description naming convention and commit with a Conventional Commit message.

Frequently Asked Questions about git-workflow-skill

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

FAQPage Schema

How do I enforce conventional commits and prevent direct commits to the develop branch?▼

To enforce conventional commits and prevent direct commits to develop, you need a standardized Git workflow that mandates feature branches and validates commit message formats before pull requests are merged.

What is the correct branch naming convention for feature branches and bugfixes?▼

The correct branch naming convention uses prefixes like feature/, bugfix/, or chore/ followed by a short description. This Git workflow validates branch names to maintain a clean repository structure and prevent direct pushes to develop.

Does this Git workflow support Jira integration for linking branches to tickets?▼

Yes, this Git workflow supports optional Jira integration to link branches with tasks. When Jira integration is available, it automatically associates your feature branches and pull requests with the corresponding Jira tickets.

How do I sync my feature branch with develop before opening a pull request?▼

To sync your feature branch with develop before opening a pull request, you perform a rebase. This Git workflow guides safe branching operations including checkout, branch creation, and rebasing with develop to ensure clean merges.

Can I use this branching strategy validation without any external dependencies?▼

Yes, you can use this branching strategy validation without external dependencies. Jira integration is optional and only activates when available, while branch safety checks and Conventional Commits enforcement function independently across your software projects.

Why should I use conventional commits in my Git workflow?▼

You should use Conventional Commits in your Git workflow to maintain a clean, scannable project history. Standardized commit messages enable automated changelog generation and make it easier to track feature additions, bug fixes, and chores across the codebase.