Git Workflow Patterns

Use this skill when working on branching, PRs, commits, or releases. Triggers on: branch naming, PR workflow, commit messages, release strategy, or mentions of "branch", "PR", "commit", "release", "versioning", "changelog", or "git workflow".

majiayu000 Updated 567 repo stars

File contents

Git Workflow — DoclingOptimisation

Branching (GitHub Flow)

  • main is always deployable
  • Short-lived feature branches: feature/, fix/, chore/, docs/
  • Branch from main, merge back to main
  • Delete branches after merge

Commits (Conventional)

  • Format: type(scope): description
  • Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore
  • Enforced by commit-message.sh hook
  • Body explains WHY, not what

Pull Requests

  • Keep PRs small and focused
  • Squash merge to main
  • Include What/Why/How/Testing sections in description

Releases

  • Semantic versioning in pyproject.toml
  • Docker image tags follow semver
  • Git tags trigger CI/CD deployment

majiayu000/claude-skill-registry-data/tree/main/devops/git-workflow-patterns commit 01fb8a18db

Frequently asked questions

npx skillmds@latest add majiayu000/git-workflow-patterns