skills.rest
vendeesign
vendeesignCOMMUNITY
Explore all skills by this author →
Website𝕏@vendeesignGitHub

git-conventions

Enforces conventional Git commit formats, branch naming, and PR messaging standards.

Updated Aug 23, 2026
Search Tags:#git#guardrails#conventional-commits#branch-naming#destructive-operations#pr-messages
One-click install
npx skills add https://github.com/vendeesign/codebloom --skill git-conventions-vendeesign
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-conventions
Source: https://github.com/vendeesign/codebloom/tree/main/skills/git-conventions
Command: npx skills add https://github.com/vendeesign/codebloom --skill git-conventions-vendeesign

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent Git histories, ambiguous commits, and risky operations undermine collaboration. This skill enforces conventional commits, standardized branch naming, consistent PR messages, and guardrails against destructive actions outside the /codebloom:push flow.

Core Features & Use Cases

  • Enforces conventional commit formats (type(scope): description) to improve traceability.
  • Standardizes branch naming conventions and PR messages for clearer collaboration.
  • Provides guardrails to warn or block destructive operations and guide code reviews.

Quick Start

Configure your repository to start enforcing git-conventions during everyday Git workflows.

Frequently Asked Questions about git-conventions

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

FAQPage Schema
How do I enforce conventional commit formats in my Git workflow?▼

To enforce conventional commit formats, this skill validates that your Git commit messages strictly follow the type(scope): description structure, ensuring clearer project traceability and standardized histories.

What is the best way to standardize branch naming conventions across a development team?▼

Standardizing branch naming conventions is achieved by applying guardrails that validate branch names against predefined rules during everyday Git operations, ensuring consistent collaboration and clearer PR messaging.

Can I block destructive Git operations like risky merges or pushes outside of my standard flow?▼

Yes, you can block destructive Git operations. The skill provides guardrails to warn or block risky commands during merges and pushes, especially when operating outside the /codebloom:push flow.

Does this skill require any dependencies to start validating PR messages and commit formats?▼

No dependencies are required to validate PR messages and commit formats. You simply configure your repository to start applying the guardrails during standard Git workflows.

Why should I use conventional commits and branch guardrails instead of standard Git commands?▼

Using conventional commits and branch guardrails prevents inconsistent Git histories and ambiguous commits, overcoming the collaboration and safety problems inherent in unregulated standard Git commands.

Related Skills

Explore More Software Engineering Skills→
IAmKongHaiIAmKongHai

ce-clean-gone-branches

Remove local branches and worktrees deleted from the remote repository.

Community
Basic
OnClickListener2048OnClickListener2048

chinese-commit-conventions

Enforce Chinese commit conventions and generate changelogs from Git history.

Community
Intermediate
vuralserhat86vuralserhat86
43

code_review

Execute code review checklists for functionality, quality, security, and performance.

Community
Intermediate
zaeem-rafiqzaeem-rafiq

git-guardrails

Block destructive git operations with pre-commit and pre-push hooks.

Community
Advanced