git-workflow

Guide Git branching and commit conventions for collaborative development.

2|Updated Oct 25, 2025

Search Tags:#git #workflow #code review #version control #commit messages #branching

Ready to run

npx skills add https://github.com/calevans/staticforge --skill git-workflow-calevans

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides clear guidelines and commands for managing your project's version control, ensuring consistent and efficient Git usage.

Core Features & Use Cases

Branching Strategy: Understand and implement the project's branching model (main, develop, feature, fix, hotfix).
Commit Standards: Adhere to Conventional Commits for clear, searchable commit history.
Workflow Guidance: Follow step-by-step instructions for starting new work, making commits, pushing, merging, and releasing.
Use Case: When starting a new feature, use this Skill to create a feature/ branch, make well-formatted commits, and understand how to merge it back into develop.

Quick Start

Use the git-workflow skill to create a new feature branch named 'user-profile-page'.

Frequently Asked Questions about git-workflow

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

FAQPage Schema

What is a structured git workflow for collaborative software development?▼

A structured git workflow standardizes branching and commit messages to facilitate code reviews and maintain a clean project history. It guides developers through feature, bugfix, and hotfix branches alongside release procedures.

How do I create a feature branch using a conventional git workflow?▼

To create a feature branch, follow the workflow guidance to branch from develop using a feature prefix, make well-formatted commits, and merge it back into develop. This isolates new work while keeping the main branch stable.

How should I format commit messages for a clean version control history?▼

Format commit messages using Conventional Commits standards to ensure a clear, searchable project history. This involves structuring messages with specific prefixes to denote features, fixes, or breaking changes.

When do I need to use hotfix branches in a version control workflow?▼

Use hotfix branches when addressing critical issues in production. The git workflow isolates urgent fixes from ongoing development, allowing you to patch the main branch directly and then merge the resolution back into develop.

Does this git workflow strategy support both bugfix and feature branches?▼

Yes, this git workflow supports feature, bugfix, and hotfix branches. It provides specific instructions for branching, making commits, pushing, merging, and releasing to maintain consistency across collaborative projects.