moai-ref-git-workflow

Consolidate Git branching, commit, and pull request practices into a reference guide.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/gkswls5006-web/last-todo --skill moai-ref-git-workflow-gkswls5006-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-ref-git-workflow
Source: https://github.com/gkswls5006-web/last-todo/tree/main/.claude/skills/moai-ref-git-workflow
Command: npx skills add https://github.com/gkswls5006-web/last-todo --skill moai-ref-git-workflow-gkswls5006-web

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralize and standardize Git workflow knowledge to reduce onboarding time, miscommunication, and release delays by providing a concise reference for branching, commits, and PR practices.

Core Features & Use Cases

  • GitHub Flow, GitFlow, and Trunk-Based development patterns with example branch trees and PR lifecycles.
  • Clear branch naming conventions (feat/, fix/, refactor/, docs/, chore/) to improve traceability and review efficiency.
  • Conventional commits and pull request templates to enforce consistent messages and review checklists.
  • Git safety and merge strategy guidance to prevent destructive actions and maintain project history.

Quick Start

Adopt a GitHub Flow workflow by creating feature branches from main and opening pull requests for review before merging.

Frequently Asked Questions about moai-ref-git-workflow

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

FAQPage Schema
What is the best way to standardize Git workflows for a software team?

Standardize Git workflows by centralizing reference guides for branching, commits, and PR practices. This reduces onboarding time and miscommunication by providing clear patterns for feature development, release management, and collaboration.

How do I use conventional commits and pull request templates to enforce consistent messages?

Use conventional commits and pull request templates to enforce consistent messages and review checklists. This practice improves traceability and review efficiency by standardizing commit messages alongside structured PR descriptions.

What is a safe Git merge strategy to prevent destructive actions and maintain project history?

A safe Git merge strategy prevents destructive actions and maintains project history by applying specific guardrails during integration. Following standardized merge guidance protects repository integrity during pull request approvals and branch consolidation.

How do I set up a GitHub Flow workflow with feature branches and pull requests?

Set up a GitHub Flow workflow by creating feature branches directly from main and opening pull requests for review before merging. This simple pattern supports continuous integration while maintaining a stable main branch.