git-best-practices

Enforce safe git workflows and Conventional Commits in automated checks.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/heykvnzhao/dotfiles --skill git-best-practices-heykvnzhao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-best-practices
Source: https://github.com/heykvnzhao/dotfiles/tree/main/skills/git-best-practices
Command: npx skills add https://github.com/heykvnzhao/dotfiles --skill git-best-practices-heykvnzhao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams enforce safety and consistency in git workflows, preventing destructive actions and ensuring standardized commit messaging.

Core Features & Use Cases

  • Safety-first workflow enforcement: default read-only operations and explicit consent for destructive commands.
  • Conventional Commits guidance: enforces commit message format and types.
  • Review and release support: aligns PR reviews, branching, and tagging with safe practices.
  • Use Case: When merging feature branches, ensure no force-push without consent.

Quick Start

Configure the git-best-practices policy in your repository and run the enforcement checks to start safe git operations.

Frequently Asked Questions about git-best-practices

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

FAQPage Schema
How do I prevent accidental destructive git actions like force-push during branch merges?

Prevent destructive git actions by enforcing safe-by-default workflows that apply read-only operations and require explicit consent for force-pushes and merges. This keeps branch operations predictable and protected during collaboration.

How do I enforce Conventional Commits format in automated git checks?

Enforce Conventional Commits format in automated checks by applying a policy that validates commit message types and structures before operations are completed. This standardizes commit messaging across your repository.

What is the best way to align PR reviews and tagging with safe git practices?

The best way to align PR reviews and tagging with safe git practices is to apply safety-first enforcement checks to your branching and release workflows. This ensures reviews and tags follow predictable, non-destructive operations.

Can I configure safe git workflows to require explicit consent for destructive commands?

Yes, you can configure safe git workflows to require explicit consent for destructive commands. This safety-first enforcement applies read-only defaults by default and prompts for consent before executing any destructive operations.

How do I standardize commit messaging for code development and release scenarios?

Standardize commit messaging for development and release scenarios by enforcing Conventional Commits formats within automated checks. This aligns diffs, commits, and merges with consistent message types and structures.