git-workflow

Enforce Conventional Commits, branch prefixes, and PR templates in Git workflows.

Updated Jan 26, 2026

Search Tags:#git #workflow #versioning #branching #code-review #pull-requests #conventional-commits

Ready to run

npx skills add https://github.com/theofernandezz/ai-library --skill git-workflow-theofernandezz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/theofernandezz/ai-library/tree/main/.opencode/skills/git-workflow
Command: npx skills add https://github.com/theofernandezz/ai-library --skill git-workflow-theofernandezz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes Git history and collaboration practices by enforcing consistent commit messages, branch naming, and pull request guidelines, improving traceability, reviews, and release reliability.

Core Features & Use Cases

Conventional commits taxonomy (feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert) to clearly convey intent.
Branching strategy with prefixes (feature/, fix/, hotfix/, release/) to organize work and automate workflows.
Pull Request templates and review checklists to ensure consistent reviews and stable integrations.
Guidance on merge strategies (squash, rebase, merge) to maintain a clean history and predictable releases.
Versioning and release workflows to manage changes and communications across teams.

Quick Start

Begin by configuring your repository to enforce Conventional Commits and a feature-branch workflow for all new work.

Frequently Asked Questions about git-workflow

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

FAQPage Schema

How do I enforce Conventional Commits in my Git workflow?▼

You can enforce Conventional Commits by applying a commit type taxonomy including feat, fix, docs, and refactor, while using branch prefixes and hooks to maintain guardrails for consistent history.

What is the best branching strategy for feature work and bug fixes?▼

An effective branching strategy uses prefixes like feature/, fix/, hotfix/, and release/ to organize work, automate workflows, and maintain predictable releases across repositories.

How do I standardize code reviews with pull request templates?▼

You standardize code reviews by applying pull request templates and review checklists, which ensures consistent reviews and stable integrations across your software development team.

Which merge strategy should I use to maintain a clean Git history?▼

To maintain a clean Git history, evaluate squash, rebase, and merge strategies based on your release needs, ensuring predictable releases and clear traceability for your development team.

Does this Git workflow approach work for multiple repositories?▼

Yes, this Git workflow approach works for multiple repositories by standardizing branch naming, commit taxonomy, and PR practices to manage changes and communications across teams.

When do I need a versioning and release workflow in Git?▼

You need a versioning and release workflow in Git when managing changes across teams, using conventional commits and merge strategies to communicate updates and ensure release reliability.