Git Workflow

Manage Git branches and commits using Gitflow and Conventional Commits.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/nicanac/reforge --skill git-workflow-nicanac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Git Workflow
Source: https://github.com/nicanac/reforge/tree/main/.ai/skills/git-workflow
Command: npx skills add https://github.com/nicanac/reforge --skill git-workflow-nicanac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes and simplifies the process of managing code changes using Git, ensuring consistency and clarity in your development workflow.

Core Features & Use Cases

  • Branch Management: Guides the creation of feature, fix, release, and hotfix branches according to Gitflow.
  • Commit Standards: Enforces the Conventional Commits specification for clear and structured commit messages.
  • Workflow Guidance: Provides clear instructions for branching, committing, and merging practices.
  • PR Template: Offers a structured template for creating effective pull requests.
  • Use Case: When starting a new feature, use this skill to create a feature/user-authentication branch and then commit your changes using messages like feat(auth): add login endpoint.

Quick Start

Create a new feature branch named 'add-user-profile' from the develop branch.

Frequently Asked Questions about Git Workflow

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

FAQPage Schema
How do I create feature and hotfix branches following Gitflow?

Gitflow branching structures development by guiding the creation of feature, fix, release, and hotfix branches from defined main and develop branches, ensuring organized code changes and protected branch rules.

What is the Conventional Commits specification for structuring commit messages?

Conventional Commits enforces structured commit messages using types like feat and fix, such as feat(auth): add login endpoint, to standardize code changes and clarify development workflow history.

How do I format a pull request template for Gitflow branching?

A pull request template for Gitflow provides a structured format for submitting feature, fix, release, and hotfix branches, ensuring merge requests meet branch protection rules and commit standards.

Can I use Gitflow and Conventional Commits for my existing Git repository?

Yes, applying Gitflow and Conventional Commits standardizes existing Git repository operations by enforcing structured commit messages and guiding branch creation without requiring additional dependencies.

What is the best way to manage release branches with Gitflow?

Gitflow manages release branches by providing clear instructions for branching, committing, and merging practices, ensuring release preparation adheres to defined branch protection rules alongside feature and hotfix branches.