skills.rest
AsyrafHussin
AsyrafHussinCOMMUNITY
Explore all skills by this author →
Website𝕏@asyrafhussin4GitHub

git-workflow

Generate commit, branch, and pull request workflow guidance for git hygiene.

62|9|Updated Jan 16, 2026
Search Tags:#git#workflow#commit#branching#code-review#pull-request
One-click install
npx skills add https://github.com/AsyrafHussin/agent-skills --skill git-workflow-asyrafhussin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/AsyrafHussin/agent-skills/tree/main/skills/git-workflow
Command: npx skills add https://github.com/AsyrafHussin/agent-skills --skill git-workflow-asyrafhussin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear, consistent git practices to help teams write meaningful commits, manage branches, and govern PRs, reducing merge conflicts and messy histories.

Core Features & Use Cases

  • Commit conventions: Conventional commits, atomic commits, imperative mood, meaningful subject lines, commit bodies, and issue references
  • Branching strategies: Naming conventions, feature branches, protected main, short-lived branches, and cleanup of merged branches
  • PR practices: Small focused PRs, review templates, reviewer assignment, CI checks, and squash merges
  • History management & collaboration: Rebase vs merge, tagging releases, and clear team collaboration norms

Quick Start

Start by applying the commit, branch, and PR rules to your project to establish a disciplined, maintainable Git workflow.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
What is a conventional commit and how does it improve git workflow?▼

A conventional commit uses structured formats like imperative mood and meaningful subject lines to create clear git history. This workflow practice reduces merge conflicts and improves team collaboration.

How do I create a pull request template for code review?▼

To create a pull request template, define review checklists, reviewer assignments, and CI check rules. This PR practice standardizes code review and ensures small focused PRs for safer collaboration.

What is the best way to name feature branches in git?▼

The best way to name feature branches is applying consistent naming conventions and keeping branches short-lived. This strategy protects the main branch and simplifies cleanup of merged branches.

When should I use rebase vs merge for git history management?▼

Use rebase to maintain linear history or merge to preserve branch context. Choosing between rebase vs merge depends on team collaboration norms and helps manage tagging releases and reducing merge conflicts.

Does this git workflow guidance apply to small software projects?▼

Yes, this git workflow guidance applies to software projects of all sizes. It scales commit conventions, branching strategies, and PR practices to establish disciplined collaboration regardless of project scale.

Related Skills

Explore More Software Engineering Skills→
Gaku52Gaku52
6

git-workflow

Establish and enforce Git workflows with branching, commit, and PR conventions.

Community
Advanced
mvillmowmvillmow
18

verify-pr-ready

Verify GitHub pull requests for CI checks, approvals, and merge conflicts.

Community
Basic
efiadmefiadm

git-hooks-setup

Automate Git hook setup with Husky, lint-staged, and commitlint.

Community
Intermediate
sachinnair90sachinnair90

release-process

Coordinate safe software releases with semver, Git tags, GitHub Releases, and npm publication.

Community
Advanced