git

Enforce Git branch, commit, and push conventions with safety guards.

13|2|Updated Aug 9, 2025
One-click install
npx skills add https://github.com/petbrains/mvp-builder --skill git-petbrains
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/petbrains/mvp-builder/tree/main/.claude/skills/git
Command: npx skills add https://github.com/petbrains/mvp-builder --skill git-petbrains

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces repository conventions for branches, commits, and pushes, including secret protection and safety guards to prevent risky actions.

Core Features & Use Cases

  • Branch typing and naming conventions (e.g., feature/, fix/, hotfix/*)
  • Commit message formatting and discipline
  • Secret/credential protection with pre-commit checks
  • Safety guards to prevent pushing to protected branches or amending pushed commits
  • Interactive prompts when intent is ambiguous

Quick Start

Trigger during git operations: create branches, commit changes, push, merge, and open PRs. Example: create a feature/alpha/login branch, commit with [KEY-123] feature(alpha): add login, then push and open a PR.

Frequently Asked Questions about git

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

FAQPage Schema
How do I enforce branch naming conventions in my Git workflow?

Branch naming conventions organize repositories by type prefix (feature/, fix/, hotfix/, etc.) and enforce structure during branch creation. This Skill applies naming rules automatically, ensuring branches follow repository standards and improving discoverability across feature, fix, refactor, docs, chore, hotfix, and release workflows.

What's the best way to prevent accidental commits with secrets or credentials?

Pre-commit checks detect and block secrets before they're committed to the repository. This Skill scans commits against credential patterns, stopping dangerous operations and ensuring sensitive data never reaches pushed history, protecting your codebase from exposure.

How do I enforce consistent commit message formatting across my team?

Commit message rules standardize format and content during commit formulation, requiring discipline around commit types and structure. This Skill applies these rules automatically, creating auditable, consistent commit history that integrates with your branching workflow.

Can I prevent pushing to protected branches or amending commits already pushed?

Safety guards block risky Git operations like pushing to protected branches or amending commits already in remote history. This Skill enforces these protections during push attempts and merge operations, preventing accidental damage to shared branch state.

Does this work with pull request and merge workflows?

Yes. The Skill applies conventions during branch creation, commits, pushes, merges, and conflict resolution. It supports feature, fix, refactor, docs, chore, hotfix, and release workflows with consistent enforcement across the entire pull request lifecycle.

What happens when branch or commit intent is ambiguous?

Interactive prompts clarify intent when operations don't clearly match repository conventions. The Skill guides users through branch type selection, commit categorization, and other decisions, reducing friction while maintaining standards compliance.