skills.rest
yolo-labs-hq
yolo-labs-hqOFFICIAL
Explore all skills by this author →
Website𝕏@yololabsaiGitHub

git-workflow

Enforce conventional commits, branch naming, and PR structure in Git workflows.

1|Updated Apr 28, 2026
Search Tags:#git#workflow#branching#best-practices#code-review#pull-request#conventional-commits
One-click install
npx skills add https://github.com/yolo-labs-hq/yolo-skills-registry --skill git-workflow-yolo-labs-hq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/yolo-labs-hq/yolo-skills-registry/tree/main/skills/git-workflow
Command: npx skills add https://github.com/yolo-labs-hq/yolo-skills-registry --skill git-workflow-yolo-labs-hq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional development workflows often lead to oversized commits, confusing branch names, and PRs that are hard to review. This Skill provides guidelines to keep commits small and meaningful, enforce consistent branch naming, and structure PRs for efficient reviews.

Core Features & Use Cases

  • Conventional commits: standardize commit messages to convey intent.
  • Branch naming: enforce type/scope prefixes for quick context.
  • PR etiquette: guidance on PR bodies and review flow to speed up approvals.

Quick Start

Create a feature branch with a descriptive type/scope, commit changes with a conventional message, and open a PR after CI passes.

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 in my Git workflow?▼

To enforce conventional commits in your Git workflow, you need guidelines that standardize commit messages to convey intent. This Skill provides automated guidance to keep commits small and meaningful by enforcing consistent commit message structures across feature development and bug fixes.

What is the best way to structure a pull request for efficient code reviews?▼

The best way to structure a pull request for efficient code reviews is to follow PR etiquette guidance with well-structured PR bodies and a logical review flow. This enforces PR quality and pre-merge checks to speed up approvals and keep PRs review-friendly.

How do I standardize branch naming with type and scope prefixes?▼

You can standardize branch naming by enforcing type and scope prefixes for quick context. This Skill implements a best-practice policy for branch naming, ensuring consistent prefixes across feature branches and bug fixes to streamline your Git workflow.

Can I use this Git workflow guidance for both feature development and bug fixes?▼

Yes, you can use this Git workflow guidance for both feature development and bug fixes. It works across these development scenarios to enforce best-practice policies for branch naming, commit messages, and PR structure, ensuring clean commits throughout your workflow.

Why do my oversized commits make pull requests hard to review?▼

Oversized commits make pull requests hard to review because they obscure intent and overwhelm reviewers. This Skill solves this by providing guidelines to keep commits small and meaningful, enforcing conventional messages and PR etiquette to speed up approvals.

Related Skills

Explore More Software Engineering Skills→
Tx1207Tx1207
5

project-creator

Create a new project from a template, initialize uv, and configure a local Git repository.

Community
Advanced
jankneumannjankneumann

linear-cleanup-feature

Merge approved OpenSpec feature pull requests and archive proposals.

Community
Advanced
I-SynergyI-Synergy

code-reviewer

Review .NET code for Clean Architecture, CQRS, SOLID, and security compliance.

Official
Advanced
NextSpark-jsNextSpark-js

github

Automates Git/GitHub workflows including branching, commit formatting, and PR creation.

Official
Advanced