skills.rest
ChoshimWy
ChoshimWyCOMMUNITY
Explore all skills by this author →
GitHub

git-workflow

Enforce branch naming, Conventional Commits, and PR templates for Git workflows.

8|Updated Feb 12, 2026
Search Tags:#git#workflow#gitignore#conventional-commits#branch-naming#pr-descriptions
One-click install
npx skills add https://github.com/ChoshimWy/iOSAgentSkills --skill git-workflow-choshimwy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/ChoshimWy/iOSAgentSkills/tree/main/skills/git-workflow
Command: npx skills add https://github.com/ChoshimWy/iOSAgentSkills --skill git-workflow-choshimwy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consistent Git practices reduce review time, prevent merge conflicts, and improve project hygiene by standardizing branches, commits, and PR descriptions across teams.

Core Features & Use Cases

  • Standard branch naming conventions (feature/<ticket-id>-<description>, bugfix/<ticket-id>-<description>, hotfix/<ticket-id>-<description>, release/<version>, refactor/<short-description>).
  • Conventional Commit style enforcement for commit messages and a PR description template.
  • Guidance on .gitignore and general Git operations to maintain clean repositories.
  • Note: This skill does not automate PR submission using GitHub CLI; for end-to-end PR flows see gh-pr-flow.

Quick Start

Set up the repository to adopt the standard branch naming, Conventional Commit messages, and PR templates as described.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I standardize Git branch naming conventions across my team?▼

Standardize Git branch naming by enforcing prefixes like feature/, bugfix/, hotfix/, release/, and refactor/ paired with ticket IDs or short descriptions. This improves project hygiene, reduces merge conflicts, and accelerates code review times across small to large projects.

What is the best way to format commit messages for clean Git history?▼

Formatting commit messages using the Conventional Commits standard is the best way to maintain a clean Git history. This Skill enforces Conventional Commit styles for messages and provides PR description templates to ensure consistent communication across teams.

How do I configure .gitignore for iOS and macOS repositories?▼

Configure .gitignore for iOS and macOS repositories by applying ignore rules that filter out common system and project noise. This Skill provides guidance on .gitignore configurations specifically tailored to maintain clean repositories for Apple platforms.

Can this Skill automate PR submission using GitHub CLI?▼

No, this Skill does not automate PR submission using GitHub CLI. It focuses on standardizing branch naming, Conventional Commit messages, and PR description templates for everyday Git operations, rather than end-to-end automated PR flows.

What Git workflow standards should a large development team adopt?▼

Large development teams should adopt Git workflow standards that include structured branch naming conventions, Conventional Commits for messages, and standardized PR description templates. This reduces review time, prevents merge conflicts, and improves overall project hygiene.

Related Skills

Explore More Software Engineering Skills→
netanel-abergelnetanel-abergel
5

git-backup

Back up OpenClaw workspace files to a GitHub repository.

Community
Intermediate
shirulotshirulot

yeet

Automate Git staging, committing, and GitHub pull request creation.

Community
Advanced
avvaleavvale

conventional-commits

Validate commit messages against the Conventional Commits specification.

Official
Basic
eysenfalkeysenfalk

git-workflow

Enforce Git branch naming, commit message formats, and merge policies.

Community
Advanced