git-practices

Validate Git branch names, commit messages, and pull requests against workflow rules.

12|1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/ovargas/virtual-team --skill git-practices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-practices
Source: https://github.com/ovargas/virtual-team/tree/main/skills/git-practices
Command: npx skills add https://github.com/ovargas/virtual-team --skill git-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent Git workflows lead to confusing history, messy reviews, and harder collaboration. This skill codifies branch naming, commit message formats, and PR etiquette to ensure clarity and traceability across projects.

Core Features & Use Cases

  • Branch naming conventions with types: feat, fix, refactor, chore
  • Commit message formatting including scope and an optional ticket id
  • Pull request etiquette and workflow guidance for streamlined reviews
  • Use case: enforce ticket-id in branch names and provide descriptive commits to accelerate reviews

Quick Start

Apply the git-practices rules to every branch, commit, and PR in your repository.

Frequently Asked Questions about git-practices

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

FAQPage Schema
How do I standardize branch naming conventions for feature and fix workflows?

Standardize branch naming by enforcing prefixes like feat, fix, refactor, and chore. This ensures consistent categorization, making it easier to track changes and maintain a clean repository history across different projects and teams.

What's the best way to format commit messages for better pull request reviews?

Format commit messages by including a clear scope and an optional ticket ID. This approach accelerates pull request reviews by providing traceability and context directly in the commit history, making it easier for reviewers to understand changes.

How do I include ticket IDs in git branches and commit messages?

Include ticket IDs in git branches and commit messages by validating ticket-like identifiers during the workflow. This enforces traceability, ensuring that every commit and branch can be linked back to a specific issue or task in your project tracker.

Can I apply consistent git workflow rules across multiple projects?

Yes, you can apply consistent git workflow rules across multiple projects. The skill codifies branch naming, commit message formats, and PR etiquette, providing automated guidance that adapts to common git activities regardless of team size or project scope.

What is proper pull request etiquette for streamlined code reviews?

Proper pull request etiquette involves following standardized branch types and descriptive commit messages. This practice streamlines code reviews by ensuring reviewers receive well-organized, traceable changes that adhere to established project conventions.