git-manager

Generate semantic Git commit messages and provide branching strategy guidance.

54|21|Updated Feb 12, 2026

Search Tags:#git #developer tools #version control #commit #branching #code management

Ready to run

npx skills add https://github.com/Nhqvu2005/VibeGravityKit --skill git-manager-nhqvu2005

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-manager
Source: https://github.com/Nhqvu2005/VibeGravityKit/tree/main/VibeGravityKit/.agent/skills/git-manager
Command: npx skills add https://github.com/Nhqvu2005/VibeGravityKit --skill git-manager-nhqvu2005

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill standardizes Git commit messages and provides clear branch strategy guidelines, enhancing project visibility and maintainability for the Leader.

Core Features & Use Cases

Semantic Commits: Enforces a structured commit message format (feat: ..., fix: ...) for better tracking of changes.
Branch Strategy Guidance: Offers different Git branching models (GitHub Flow, Git Flow, Trunk-Based) to suit team needs.
Leader Report: Provides a summarized view of project history.
Use Case: Ensure all new features are committed with feat(scope): message and bug fixes with fix(scope): message for clear project history.

Quick Start

Use the git-manager skill to make a new feature commit with the message "Implement user authentication".

Frequently Asked Questions about git-manager

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

FAQPage Schema

How do I automate semantic commit messages for git feature branches?▼

Automating semantic commit messages enforces structured formats like feat, fix, and refactor for better project tracking. This skill generates standardized messages and logs project history to maintain clear code management visibility.

What is the best way to enforce a semantic commit format like feat or fix?▼

Enforcing a semantic commit format standardizes git history by requiring structured prefixes like feat, fix, docs, or refactor. This ensures clear tracking of changes and improves overall project maintainability for developers.

How do I choose a git branching strategy for my development team?▼

Choosing a git branching strategy involves evaluating models like GitHub Flow, Git Flow, or Trunk-Based Development. This skill provides guidance on these strategies to match your team's specific workflow needs and improve code management.

Can I generate a project history report from structured git commits?▼

Generating a project history report from structured git commits provides a summarized view of changes. This skill uses semantic conventions to log project history, offering clear visibility into features and bug fixes for reporting.

Do I need any specific git tools or dependencies to use semantic commits?▼

No specific git dependencies are required to use semantic commits with this skill. It operates independently to enforce structured commit message formats and provide branching strategy guidance without external developer tool integrations.

When should I use Trunk-Based Development over Git Flow for version control?▼

Use Trunk-Based Development over Git Flow when you need a more streamlined branching strategy for continuous integration. This skill provides guidance on selecting between these version control models based on your project's structure and team needs.