rulebook-git-workflow

hivellm's avatarfrom hivellm

Git workflow standards including branching strategy, commit conventions, and PR guidelines. Use when creating branches, writing commit messages, preparing pull requests, or following git best practices.

⭐5stars🔀0forks📁View on GitHub🕐Updated Dec 10, 2025

When & Why to Use This Skill

This Claude skill provides a comprehensive framework for Git workflow management, ensuring consistency across development teams. It enforces standardized branch naming conventions, Conventional Commit formats, and structured Pull Request guidelines. By integrating these best practices, teams can improve repository maintainability, facilitate easier debugging through clear history, and enhance the overall quality of the software development lifecycle (SDLC).

Use Cases

  • Standardizing Branch Creation: Automatically generate branch names like 'feature/task-id-description' to maintain a clean and searchable repository structure.
  • Conventional Commit Authoring: Assist developers in crafting professional commit messages that follow the type(scope): subject format, enabling automated changelog generation.
  • Pull Request Preparation: Generate detailed PR descriptions with summaries, change lists, and testing checklists to improve code review efficiency and communication.
  • Team Onboarding and Compliance: Serve as an interactive guide for new team members to ensure all contributions align with established organizational Git standards and best practices.
namerulebook-git-workflow
descriptionGit workflow standards including branching strategy, commit conventions, and PR guidelines. Use when creating branches, writing commit messages, preparing pull requests, or following git best practices.
version"1.0.0"
categorycore
author"HiveLLM"
tags["git", "workflow", "branching", "commits", "pull-requests"]
dependencies[]
conflicts[]

Git Workflow Standards

Branch Naming

feature/<task-id>-<short-description>
fix/<issue-id>-<short-description>
refactor/<scope>-<description>
docs/<scope>-<description>

Commit Message Format

<type>(<scope>): <subject>

<body>

<footer>

Types

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation
  • style: Formatting
  • refactor: Code restructuring
  • test: Adding tests
  • chore: Maintenance

Example

feat(auth): add JWT token validation

Implement JWT validation middleware for protected routes.

Closes #123

Pull Request Guidelines

PR Title

feat(scope): short description

PR Description

## Summary
Brief description of changes.

## Changes
- Change 1
- Change 2

## Testing
How this was tested.

## Checklist
- [ ] Tests pass
- [ ] Lint passes
- [ ] Documentation updated

Workflow Steps

  1. Create feature branch from main
  2. Make commits following conventions
  3. Run quality checks before push
  4. Create PR with description
  5. Address review feedback
  6. Squash and merge