skill-git

Enforce Git branching, commit conventions, and release workflows across repositories.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/claudioborja/biblioteca --skill skill-git
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-git
Source: https://github.com/claudioborja/biblioteca/tree/main/.agents/skills/skill-git
Command: npx skills add https://github.com/claudioborja/biblioteca --skill skill-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines and standardizes advanced Git workflows across teams, enabling consistent branching, commits, and releases to reduce merge conflicts and confusion.

Core Features & Use Cases

  • Workflow enforcement: standardizes branching models (GitFlow, GitHub Flow, trunk-based) and ensures commit-conventions are followed.
  • Commit hygiene: enforces Conventional Commits or semantic versioning, improving release notes and changelogs.
  • Recovery & safety: provides guidance on rebasing, reflog recovery, and safe history rewrites to minimize risk.
  • Use Case: In a multi-team project, apply the recommended Git workflow to coordinate feature development, bug fixes, and release tagging across repositories.

Quick Start

Apply a modern Git workflow (GitFlow, GitHub Flow, or trunk-based) to your repository and align branches, commits, and releases accordingly.

Frequently Asked Questions about skill-git

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

FAQPage Schema
How do I enforce consistent Git branching strategies across multiple repositories?

To enforce consistent Git branching across repositories, apply standardized workflow models like GitFlow, GitHub Flow, or trunk-based development. This standardizes branch structures and release coordination to reduce merge conflicts and team confusion.

What is the best way to standardize commit messages for automated release notes?

The best way to standardize commit messages for release notes is to enforce Conventional Commits. Applying semantic versioning and commit conventions improves changelog generation and maintains consistent release tracking across development teams.

How do I safely perform Git rebasing without losing commit history?

To safely perform Git rebasing without losing history, use guided reflog recovery practices and enforce guardrails against unsafe history rewrites. This minimizes risk and provides recovery options during complex rebase operations.

Can I manage Git submodules within a trunk-based development workflow?

Yes, you can manage Git submodules within a trunk-based development workflow. The workflow supports submodule coordination across multiple repositories, ensuring consistent feature development, bug fixes, and release tagging within your chosen branching model.

When should I choose GitFlow over GitHub Flow for version control?

Choose GitFlow over GitHub Flow when your version control workflow requires structured release branches and long-term maintenance. GitFlow supports complex release tagging across multiple repositories, while GitHub Flow suits simpler, continuous deployment branching models.

Why do my Git workflows result in frequent merge conflicts in multi-team projects?

Git workflows result in frequent merge conflicts in multi-team projects when branching strategies and commit conventions are not standardized. Enforcing a consistent model like trunk-based development aligns branches and reduces integration conflicts.