skills.rest
michaelsvanbeek
michaelsvanbeekCOMMUNITY
Explore all skills by this author →
GitHub

git-workflow

Codify Git commit, branch, and PR practices with Conventional Commits.

1|2|Updated Apr 9, 2026
Search Tags:#git#workflow#branching#code-review#pull-requests#conventional-commits#commit-messages
One-click install
npx skills add https://github.com/michaelsvanbeek/personal-agent-skills --skill git-workflow-michaelsvanbeek
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/michaelsvanbeek/personal-agent-skills/tree/main/skills/git-workflow
Command: npx skills add https://github.com/michaelsvanbeek/personal-agent-skills --skill git-workflow-michaelsvanbeek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git workflow confusion and inconsistent commit history slow development and hinder collaboration; this skill codifies best practices to keep history clean and reviews efficient.

Core Features & Use Cases

  • Conventional commits: Standardizes commit messages to enable automated changelogs and semantic versioning.
  • Branch naming conventions: Enforces consistent, descriptive branch names for features, fixes, and releases.
  • PR descriptions templates: Guides PR descriptions for quick reviews and traceability.
  • Changelog alignment: Ensures release notes reflect changes consistently.

Quick Start

Apply the Conventional Commits and branch naming standards to your next feature work.

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 codifying commit, branch, and pull request practices. This approach enforces Conventional Commits, branch naming conventions, and PR templates to keep history clean and reviews efficient.

How do I enforce Conventional Commits and branch naming conventions?▼

You enforce Conventional Commits and branch naming conventions by applying standardized guidelines to daily feature branching. This standardizes commit messages and enforces consistent, descriptive branch names for features, fixes, and releases.

How do I write PR descriptions for quick code reviews and traceability?▼

Writing PR descriptions for quick reviews requires using guided PR description templates. These templates ensure your pull request descriptions provide necessary context for traceability and efficient code review.

Does standardizing commit messages help with changelog alignment?▼

Standardizing commit messages with Conventional Commits directly enables changelog alignment. It ensures release notes reflect changes consistently and allows for automated changelogs and semantic versioning.

Why does inconsistent Git commit history hinder development collaboration?▼

Inconsistent Git commit history hinders collaboration because it causes workflow confusion and slows development. Codifying best practices with standardized PR templates and commit messages keeps history clean and reviews efficient.

Can I use these Git workflow practices for feature branching and fixes?▼

Yes, these Git workflow practices apply to daily development tasks including feature branching and fixes. They enforce descriptive branch names and commit hygiene for both features and releases.

Related Skills

Explore More Software Engineering Skills→
pradeepmoulipradeepmouli
2

speckit-git-initialize

Initialize a Git repository with configurable branch and .gitignore settings.

Community
Intermediate
ccfccf

changelog-automation

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

Community
Advanced
ByronWilliamsCPAByronWilliamsCPA

Git Workflow Skill

Enforce branch validation, commit conventions, and PR preparation in Git workflows.

Official
Basic
SunS1eep1ngSunS1eep1ng

git-commit

Create local git commits using the Conventional Commits format.

Community
Intermediate