git-workflow

Enforce a standard Git workflow with branch checks, naming conventions, and PR reviews.

126|41|Updated Aug 4, 2018

Search Tags:#git #workflow #branching #code-review #pull-request #conventional-commits #branch-naming

Ready to run

npx skills add https://github.com/hiromaily/go-crypto-wallet --skill git-workflow-hiromaily

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/hiromaily/go-crypto-wallet/tree/main/.claude/skills/git-workflow
Command: npx skills add https://github.com/hiromaily/go-crypto-wallet --skill git-workflow-hiromaily

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies a standard Git workflow to ensure safe, auditable code changes across tasks and teams.

Core Features & Use Cases

Mandatory branch checks before starting work and never committing to main.
Branch naming conventions and PR creation guidelines to promote consistency.
Pre-work verification and conventional commit practices to improve traceability.
Use case: when starting a feature or bugfix, create a structured branch like feature/description-123 and submit a PR for review.

Quick Start

To begin any task, verify you're not on main, then create a feature branch and begin work:

git fetch origin git checkout main git reset --hard origin/main git checkout -b feature/{brief-description}-{issue-number}

Frequently Asked Questions about git-workflow

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

FAQPage Schema

What is a standard git workflow for creating auditable code changes?▼

A standard git workflow for auditable code changes enforces checking out from main, creating standardized feature branches, and submitting pull requests for mandatory review before merging. This prevents direct commits to main.

How do I create a feature branch with conventional naming before starting work?▼

To create a feature branch with conventional naming, verify you are not on main, then use a command like git checkout -b feature/{brief-description}-{issue-number} to ensure traceability and consistency across the team.

Why should I avoid committing directly to the main branch in a git workflow?▼

Avoiding direct commits to the main branch in a git workflow ensures safe, auditable changes by requiring a mandatory pull request review, which prevents unreviewed code from entering the production codebase.

Does a conventional commits workflow require mandatory pull request reviews?▼

Yes, a conventional commits workflow often requires mandatory pull request reviews to enforce code quality and traceability, ensuring that standardized branch naming and pre-work verification checks are properly governed.

What's the best way to verify my local main branch before starting a new feature?▼

The best way to verify your local main branch before starting a new feature is to fetch origin, checkout main, and run git reset --hard origin/main to ensure your local environment matches the repository's latest state.

Can I use this git workflow for both bugfixes and new feature development?▼

Yes, you can use this git workflow for both bugfixes and new feature development, as it applies to any task involving code changes by enforcing standardized branch creation and mandatory PR reviews.