skills.rest
kimasplund
kimasplundCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-workflow-skills

Standardize Git workflows, commit messaging, and branching strategies across teams.

4|1|Updated Jan 19, 2026
Search Tags:#git#branching#commits#workflows#code-review#pull-requests#conventional-commits
One-click install
npx skills add https://github.com/kimasplund/claude_cognitive_reasoning --skill git-workflow-skills
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow-skills
Source: https://github.com/kimasplund/claude_cognitive_reasoning/tree/main/skill-frameworks/git-workflow-skills
Command: npx skills add https://github.com/kimasplund/claude_cognitive_reasoning --skill git-workflow-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill standardizes and codifies Git workflows, commit messaging, and collaboration practices to reduce friction and ensure consistent code reviews, merges, and branching patterns across teams.

Core Features & Use Cases

  • Guided branching strategies: GitHub Flow, Git Flow, and Trunk-based Development with clear naming conventions.
  • Conventional commits guidance: Enforces consistent commit messages, subject length, and body formatting to improve traceability.
  • PR and collaboration patterns: Standard PR descriptions, review rituals, and merge vs rebase decision support for safer releases.

Quick Start

Provide your repository context to generate a standard Git workflow blueprint and a PR-ready plan.

Frequently Asked Questions about git-workflow-skills

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

FAQPage Schema
How do I standardize Git commit messages for better traceability?▼

Apply conventional commits guidance to enforce consistent commit messages, subject length, and body formatting, ensuring standardized Git workflows and improved traceability across team collaboration.

What is the best way to choose between Git Flow and Trunk-based Development?▼

Choose between Git Flow, GitHub Flow, and Trunk-based Development by evaluating guided branching strategies that provide clear naming conventions and match your team's release cadence and collaboration patterns.

How do I decide whether to merge or rebase a Git branch?▼

Decide between merge and rebase operations using standard PR practices and decision support logic designed to maintain safer releases and cleaner project history during version-control collaboration.

Does this Git workflow skill support standard PR descriptions and code review rituals?▼

Yes, it provides PR and collaboration patterns that enforce standard PR descriptions, review rituals, and merge strategies to ensure consistent code reviews and safer releases across teams.

Why use atomic commits in Git workflows?▼

Use atomic commits in Git workflows to keep changes focused and self-contained, which improves traceability, simplifies code review, and ensures consistent collaboration practices across version-control tasks.

Related Skills

Explore More Software Engineering Skills→
pradeepmoulipradeepmouli
2

speckit-git-initialize

Initialize a Git repository with configurable branch and .gitignore settings.

Community
Intermediate
sethihqsethihq

ship

Execute type checks, builds, tests, and linting before creating GitHub pull requests.

Community
Advanced
duongbui234duongbui234

finishing-a-development-branch

Verify tests, merge branches, create pull requests, and clean up Git workspaces.

Community
Advanced
1Mangesh11Mangesh1
3

npm-scripts

Orchestrate npm, yarn, and pnpm scripts across monorepo workspaces.

Community
Intermediate