git-workflows

Standardize git and GitHub workflows, commit conventions, and branch naming.

6|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/kmshihab7878/claude-code-setup --skill git-workflows-kmshihab7878
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflows
Source: https://github.com/kmshihab7878/claude-code-setup/tree/main/skills/git-workflows
Command: npx skills add https://github.com/kmshihab7878/claude-code-setup --skill git-workflows-kmshihab7878

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams and developers avoid inconsistent commits, messy branch histories, low-quality pull requests, and risky destructive git operations by codifying git and GitHub workflow patterns and conventions into a single reference.

Core Features & Use Cases

  • Commit conventions: Enforces Conventional Commits style, subject line limits, and guidance on commit scope, body, and breaking changes.
  • Branching & release strategy: Prescribes naming patterns for feature, fix, hotfix, and release branches and provides a decision tree for trunk-based, GitHub Flow, and Git Flow choices.
  • PR and conflict guidance: Recommends PR titles/descriptions, review practices, conflict-resolution approaches, and safeguards for destructive commands and repository hygiene.

Quick Start

Use the git-workflows guide to review and improve the current branch name, commit messages, and pull request description before merging.

Frequently Asked Questions about git-workflows

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

FAQPage Schema
How do I write conventional commits and structure commit messages?

Conventional commits enforce a standardized message style with subject line limits, defined scopes, structured bodies, and explicit breaking change annotations to improve repository hygiene and collaboration.

What is the best branching strategy for my git repository?

Choosing a branching strategy depends on your release cadence, using a decision tree to select between trunk-based development, GitHub Flow, and Git Flow while standardizing feature, fix, hotfix, and release branch naming patterns.

How do I resolve git merge conflicts during a pull request review?

Resolving merge conflicts during pull request reviews requires applying standardized conflict-resolution approaches to systematically integrate competing changes while maintaining branch history quality and repository safeguards.

When should I use git rebase instead of a merge commit?

Deciding between rebasing and merging depends on your workflow conventions, evaluating whether to preserve original commit history with merge commits or linearize branch history through rebasing before opening a pull request.

How do I safeguard against destructive git commands in shared branches?

Safeguarding against destructive git commands requires codifying repository hygiene rules that restrict risky operations in shared branches, preventing accidental history loss during pull request merges and conflict resolution.

What should be included in a high-quality pull request description?

A high-quality pull request description includes standardized titles, detailed context, testing information, and review checklists to reduce errors and improve collaboration during the code review process.