git-workflow

Standardizes Git commits, PRs, and branching with Conventional Commits and templates.

3|4|Updated Mar 20, 2026

Search Tags:#git #workflow #changelog #code-review #pull-requests #commit-messages #branching-strategies

Ready to run

npx skills add https://github.com/jamestorrevillas/dev-skills --skill git-workflow-jamestorrevillas

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline Git workflows by providing clear conventions for commits, PR descriptions, branching, and code reviews to reduce bike-shedding and integration friction.

Core Features & Use Cases

Enforces Conventional Commits, PR templates, and branch naming standards to improve traceability and release automation.
Guides code review etiquette and changelog generation to accelerate collaboration in software teams.
Use Case: A team wants a repeatable PR process with consistent messages and auto-generated changelogs.

Quick Start

Create a new feature branch, follow the commit guidelines, and reference PR templates to standardize reviews.

Frequently Asked Questions about git-workflow

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

FAQPage Schema

How do I standardize Git commit messages and PR descriptions for my team?▼

Standardize Git commit messages and PR descriptions by enforcing Conventional Commits and applying PR templates. This provides clear conventions to reduce bike-shedding and integration friction during code reviews.

How does Conventional Commits improve release notes and changelog generation?▼

Conventional Commits improves release notes and changelog generation by enforcing structured commit messages. This standardization enhances traceability and enables auto-generated changelogs for software teams.

What is the best way to establish a repeatable pull request and code review process?▼

The best way to establish a repeatable pull request process is to implement standardized PR templates and branching rules. This guides code review etiquette and accelerates team collaboration.

Can I use standardized branching strategies for software teams of any size?▼

Yes, you can use standardized branching strategies for software teams of any size. Applying branch naming conventions and PR templates ensures repeatable workflows and improves traceability across the team.

How do I automate changelog generation from Git workflows?▼

Automate changelog generation by enforcing Conventional Commits and standardizing PR descriptions within your Git workflows. This structured approach improves traceability and enables automatic release notes generation.