skills.rest
jgeldart
jgeldartCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-workflow

Guide Git commits, branch naming, and pull request descriptions.

Updated Jan 19, 2026
Search Tags:#git#version control#conventional commits#commit messages#branching#pull requests
One-click install
npx skills add https://github.com/jgeldart/github-copilot-plugins --skill git-workflow-jgeldart
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/jgeldart/github-copilot-plugins/tree/main/.github/skills/git-workflow
Command: npx skills add https://github.com/jgeldart/github-copilot-plugins --skill git-workflow-jgeldart

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill provides guidance to adopt clear, consistent Git workflows for commits, branches, and pull requests, reducing confusion and improving code history quality.

Core Features & Use Cases

  • Commit message guidelines and formats that promote readability and traceability.
  • Branch naming conventions and PR description structure to support collaboration on features and fixes.
  • Practical workflows for starting work, reviewing changes, and merging code in teams or solo projects.
  • Use Case: Imagine preparing a feature branch and PR for a bug fix across multiple commits; this skill guides formatting, reviews, and merge strategy.

Quick Start

Start by reviewing the commit_message.py tool to validate or generate conventional commit messages, then apply the recommended branch naming and PR guidelines to your workflow.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I write conventional commit messages for better version control history?▼

Conventional commit messages use specific types like feat or fix to structure commits, improving readability and traceability. This skill provides guidelines and a Python tool to validate or generate these formats for your Git workflow.

What is the best way to name Git branches for feature development and bug fixes?▼

The best way to name Git branches is using consistent naming conventions that reflect the work type. This skill offers branch naming templates to support clear collaboration on features and fixes across personal and team projects.

How do I structure a pull request description for a code review?▼

A well-structured pull request description outlines changes, context, and testing details clearly. This skill defines PR description standards to guide formatting and review strategies when preparing feature branches for merging.

Can I use these Git workflow guidelines for both solo and team projects?▼

Yes, you can use these Git workflow guidelines for both solo and team projects. The skill covers practical workflows for starting work, reviewing changes, and merging code that scale across everyday software development tasks.

Do I need any external dependencies to validate my commit messages?▼

No external dependencies are needed to validate your commit messages. The skill includes a standalone commit_message.py script and reference guidelines to check formatting and generate conventional commits directly.

Related Skills

Explore More Software Engineering Skills→
CongtrinhhCongtrinhh

speckit-git-initialize

Initialize a Git repository with an initial commit for new projects.

Community
Intermediate
acartineacartine
1

pull_main

Checkout the main branch and pull latest changes from the remote.

Community
Basic
hairihouhairihou

git-conventions

Enforce Conventional Commits syntax for Git commit messages and branch naming.

Community
Basic
ccfccf

changelog-automation

Generate CHANGELOG.md from commits, PRs, and releases using Keep a Changelog.

Community
Advanced