skills.rest
jjjh7401
jjjh7401COMMUNITY
Explore all skills by this author →
GitHub

moai-ref-git-workflow

Provides git workflow reference patterns for branch strategies, conventional commits, and PR templates.

Updated Jul 24, 2026
Search Tags:#git#workflow#pull request#conventional commits#merge#github flow#branch strategy
One-click install
npx skills add https://github.com/jjjh7401/AI-Lighting_Console --skill moai-ref-git-workflow-jjjh7401
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moai-ref-git-workflow
Source: https://github.com/jjjh7401/AI-Lighting_Console/tree/main/.claude/skills/moai-ref-git-workflow
Command: npx skills add https://github.com/jjjh7401/AI-Lighting_Console --skill moai-ref-git-workflow-jjjh7401

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams and agents performing git operations often lack consistent conventions for branching, commit messages, and pull requests, leading to messy histories, unsafe force pushes, and unreviewable merges. This Skill supplies a standardized reference of git workflow patterns so every branch, commit, and PR follows production-grade conventions. ## Core Features & Use Cases - Branch Strategy Patterns: Reference implementations of GitHub Flow, GitFlow, and Trunk-Based development with naming conventions like feat/SPEC-XXX-slug. - Conventional Commits Guide: A complete type table (feat, fix, refactor, chore, etc.) plus commit message structure with scope, body, and footer rules. - PR Templates and Merge Strategies: Ready-to-use pull request template and guidance on choosing squash, merge, or rebase based on branch type. - Git Safety Rules: Explicit risk table covering force push, hard reset, and hook skipping, plus red flags and verification checklists. - Use Case: When an agent or developer needs to create a feature branch and open a PR for SPEC-AUTH-001, this Skill dictates the branch name, commit format, PR body, and safe merge method. ## Quick Start Ask the AI to create a conventional-commit-compliant branch and pull request for your current feature using the git workflow reference.

Frequently Asked Questions about moai-ref-git-workflow

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

FAQPage Schema
How do I write a conventional commit message?▼

Use the format type(scope): description with a maximum of 72 characters, choosing a type like feat, fix, refactor, docs, or chore. Add an optional body explaining what and why, plus a footer for breaking changes and issue references.

What branch naming convention should I use for features?▼

Use feat/SPEC-{ID}-{slug} for new features, fix/SPEC-{ID}-{slug} for bug fixes, and prefixes like refactor/, docs/, or chore/ for other work. This ties every branch to a SPEC reference and makes history searchable.

When should I use squash merge vs merge commit?▼

Use squash merge for feature branches to keep main history clean, merge commits for release branches to preserve development narrative, and rebase for small clean commits. The active method can be governed by a git_strategy merge_method config value.

Is it safe to force push to a feature branch?▼

Force push is never allowed on main or master and is risky on shared feature branches because collaborators or CI may have fetched them. Use --force-with-lease instead, and always confirm destructive actions with the user first.

What are red flags in a git workflow?▼

Red flags include commit messages not following conventional format, force pushes to protected branches, PRs merged without passing CI, branch names lacking a feat/fix/SPEC prefix, and merge conflict markers committed to files.

Related Skills

Explore More Software Engineering Skills→
pegasus-isipegasus-isi

commit

Generate Conventional Commits from git status, diffs, and branch metadata.

Official
Intermediate
edhoferdianedhoferdian
2

git-and-release-ops-edho-ferdian

Guides Git branching, commit conventions, PR triage, and release versioning workflows.

Community
Intermediate
RamblurrRamblurr

Finishing a Development Branch

Verifies tests, formatting, and linting before creating a Pull Request.

Community
Intermediate
hung-phanhung-phan

trunk-based-development

Implement a trunk-based development workflow with short-lived branches and feature flags.

Community
Advanced