git-workflow

Automate Git workflow governance with conventional commits and PR templates.

20|3|Updated Apr 30, 2026

Search Tags:#git #workflow #branching #merge #rebase #pull-request #conventional-commits

Ready to run

npx skills add https://github.com/DVNghiem/FlowDeck --skill git-workflow-dvnghiem

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/DVNghiem/FlowDeck/tree/main/src/skills/git-workflow
Command: npx skills add https://github.com/DVNghiem/FlowDeck --skill git-workflow-dvnghiem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Branching and commit history can become inconsistent without defined conventions; this skill provides structured Git workflow guidance to enforce clean history, consistent commits, and predictable PR processes.

Core Features & Use Cases

Conventional commits format guidance and types
PR templates and merge-vs-rebase guidance
Activation triggers when starting features, opening PRs, or managing releases Use case: a team starting a new feature should follow the git-workflow skill to create a feature branch with a descriptive, atomic commits and a PR ready with a template.

Quick Start

Activate this skill when starting a feature, creating a PR, or preparing a release to apply the Git workflow guidelines.

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 commits and clean Git history across multiple branches?▼

To enforce clean Git history, this governance automation applies conventional commit formats, PR templates, and merge-vs-rebase guidance across feature development and release management branches, preventing inconsistent commits.

What is the best way to manage pull requests and prevent branch regressions?▼

The best way to manage pull requests is using structured Git workflow templates that enforce consistency, provide merge-vs-rebase guidance, and ensure predictable PR processes to prevent regressions.

When should I use a merge versus a rebase in my Git workflow?▼

Merge versus rebase guidance depends on your branching context; this workflow provides specific recommendations during feature development, PR creation, and release management to maintain predictable history.

Does this Git workflow governance support feature branching and release management?▼

Yes, this Git workflow governance explicitly supports feature branching and release management by applying structured conventions, conventional commits, and PR templates across those multiple branch types.

How do I create a feature branch with atomic commits and a PR template?▼

To create a feature branch with atomic commits, activate this workflow skill when starting features; it guides descriptive commit creation and automatically applies PR templates for auditable history.