git-workflow

Standardize Git branching, commits, and releases with conventional commits.

8|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/kensaurus/cursor-kenji --skill git-workflow-kensaurus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/kensaurus/cursor-kenji/tree/main/skills/git-workflow
Command: npx skills add https://github.com/kensaurus/cursor-kenji --skill git-workflow-kensaurus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes Git workflows to reduce merge conflicts, ensure consistent commit history, and streamline release processes across teams.

Core Features & Use Cases

  • Branching strategies guidance (GitHub Flow and GitFlow)
  • Conventional commits and PR workflow templates
  • Release tagging, changelogs, and version management
  • Code review and merge conflict resolution best practices

Quick Start

Adopt the standard branch model and conventional commit format to start your project.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
What is the best way to standardize Git workflows for team collaboration?

Standardizing Git workflows involves adopting consistent branching strategies like GitFlow or GitHub Flow, enforcing conventional commits, and applying guardrails for code review and release tagging to reduce merge conflicts and streamline releases.

How do I enforce conventional commits and pull request templates in my project?

To enforce conventional commits and pull request templates, apply standardized Git workflow processes that guide commit messaging formats and PR workflows, ensuring consistent commit history and structured code reviews across the team.

What's the difference between GitFlow and GitHub Flow branching strategies?

GitFlow and GitHub Flow are branching strategies guided by standardized workflows; GitFlow supports structured release management with multiple branch types, while GitHub Flow offers a simpler, continuous deployment model for faster release cycles.

Can I use standardized Git workflows for software projects of varying sizes?

Yes, standardized Git workflows are applicable across software projects of varying sizes, providing scalable guidance for branching, commit messaging, PR processes, releases, and merge conflict resolution.

How do I manage release tagging, changelogs, and version management with Git?

Manage release tagging and changelogs by standardizing your Git workflow to include version management practices, ensuring automated changelog maintenance and structured release tagging for consistent deployment histories.

How do I resolve merge conflicts during code review in a standardized Git workflow?

Resolve merge conflicts during code review by following standardized Git workflow best practices, which provide structured guardrails and resolution processes to maintain code integrity and consistent commit history.