skills.rest
eco2-team
eco2-teamOFFICIAL
Explore all skills by this author →
GitHub

git-workflow

Standardize Git workflows with branch strategies, naming conventions, and PR procedures.

3|Updated Oct 27, 2025
Search Tags:#git#workflow#branching#pull-request#conventional-commits#branch-naming
One-click install
npx skills add https://github.com/eco2-team/backend --skill git-workflow-eco2-team
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/eco2-team/backend/tree/main/.claude/skills/git-workflow
Command: npx skills add https://github.com/eco2-team/backend --skill git-workflow-eco2-team

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill standardizes Git workflow across teams by outlining branch strategies, naming conventions, and PR procedures.

Core Features & Use Cases

  • Branch Strategy: Define base branches, feature branches, release planning, and hotfix procedures.
  • Branch Naming Convention: Enforce consistent naming across features, fixes, refactors, and releases.
  • PR & Merge Process: Clear guidelines for creating pull requests, reviews, and merging back to develop. Use Case: A team migrating to Git Flow uses this guide to ensure predictable releases and code reviews.

Quick Start

Copy the recommended branch workflow into your repo and start creating feature branches from develop, then open PRs back to develop.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I standardize Git workflow across my development team?▼

Standardize Git workflow by defining branch strategies, naming conventions, and PR procedures. This involves using develop/main workflows, creating feature/refactor/fix branches, and enforcing PR-based merging with reviews.

What is the best way to name Git branches for features and fixes?▼

The best way to name Git branches is by enforcing consistent naming conventions across features, fixes, refactors, and releases. This ensures predictable tracking and aligns with your base branch strategy.

How does a pull request merge process work with a develop branch?▼

The pull request process works by creating feature branches from develop, opening PRs back to develop, and requiring code reviews before merging. This maintains a clear base branch and integration lifecycle.

Do I need conventional commits for a Git Flow branching strategy?▼

Yes, conventional commits are enforced within this Git Flow branching strategy. They standardize commit history, align with branch lifecycle steps, and integrate cleanly with CI/CD pipeline requirements.

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

You need hotfix branches when addressing critical issues in production releases. They are part of a complete branch strategy that defines base branches, release planning, and specific procedures for urgent fixes.

Can I integrate CI/CD pipelines with a feature branch workflow?▼

Yes, CI/CD integration is a required component of this feature branch workflow. The guidelines enforce CI/CD requirements described in the references to ensure code quality during PR reviews and merging.

Related Skills

Explore More Software Engineering Skills→
luigiinredluigiinred
1

dev-workflow-initialize

Create a Git worktree and branch from origin/main with ticket details.

Community
Advanced
ahmadawaisahmadawais

pr

Automate pull request workflows from branch creation to merge.

Community
Intermediate
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced
automacoescomerciaisintegradasautomacoescomerciaisintegradas

git-workflow

Guide Git branching strategies and merge conflict resolution for collaborative workflows.

Community
Advanced