skills.rest
elevanaltd
elevanaltdOFFICIAL
Explore all skills by this author →
GitHub

git-workflow

Enforce Conventional Commits and Git Flow branching for pull requests.

Updated Aug 23, 2026
Search Tags:#code review#collaboration#version control#commit messages#Git#branching#pull requests
One-click install
npx skills add https://github.com/elevanaltd/oa --skill git-workflow-elevanaltd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/elevanaltd/oa/tree/main/.claude/skills/git-workflow
Command: npx skills add https://github.com/elevanaltd/oa --skill git-workflow-elevanaltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent Git practices, messy commit histories, and inefficient branching strategies lead to merge conflicts, difficult code reviews, and lost context, hindering team productivity.

Core Features & Use Cases

  • Conventional Commits: Enforces a structured commit message format (type(scope): subject) for clear history, automated changelogs, and easier debugging.
  • Git Flow Branching Strategy: Guides the use of main, develop, feature/*, fix/*, release/*, and hotfix/* branches for organized development and release management.
  • Pull Request Best Practices: Provides guidelines for small, focused PRs with clear descriptions, self-reviews, and mandatory test/documentation inclusion, streamlining code review.
  • Use Case: When contributing to a project, use this skill to ensure your commits follow conventional format, your branch strategy aligns with Git Flow, and your pull requests are clear and concise, improving team collaboration and code quality.

Quick Start

Create a new feature branch from develop for issue #123, then make a commit with a conventional commit message.