skills.rest
Seung-zedd
Seung-zeddCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

moai-ref-git-workflow

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

Updated Aug 29, 2026
Search Tags:#git#workflow#pull request#conventional commits#reference#merge#branch strategy
One-click install
npx skills add https://github.com/Seung-zedd/secure-file-upload --skill moai-ref-git-workflow-seung-zedd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moai-ref-git-workflow
Source: https://github.com/Seung-zedd/secure-file-upload/tree/main/.claude/skills/moai-ref-git-workflow
Command: npx skills add https://github.com/Seung-zedd/secure-file-upload --skill moai-ref-git-workflow-seung-zedd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams and AI agents often produce inconsistent branch names, commit messages, and pull request formats, making history hard to audit and review. This Skill supplies a single reference of git workflow conventions so every branch, commit, and PR follows the same production-grade patterns. ## Core Features & Use Cases - Branch Strategy Patterns: Documents GitHub Flow, GitFlow, and Trunk-Based models with naming conventions like feat/SPEC-{ID}-{slug}. - Conventional Commits Reference: Defines commit types (feat, fix, refactor, chore, etc.), message structure, and context-embedding practices for session continuity. - PR Templates and Merge Strategy: Provides a pull request template, merge method selection (squash, merge, rebase), and git safety rules covering force push, hard reset, and hook bypassing. - Use Case: When an agent or developer creates a feature branch and opens a PR, this reference ensures the branch name, commit messages, and PR body all follow the same documented conventions. ## Quick Start Ask the agent to create a feature branch and pull request for a new SPEC following the git workflow reference conventions.

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 conventional commit messages?▼

Conventional commits follow the format type(scope): description, with types like feat, fix, refactor, test, docs, and chore. Keep the subject line under 72 characters and add an optional body explaining what and why, plus footers for breaking changes or issue references.

What branch naming convention should I use for features?▼

Use the pattern feat/SPEC-{ID}-{slug}, for example feat/SPEC-AUTH-001-jwt-auth. Other prefixes include fix/ for bug fixes, refactor/ for restructuring, docs/ for documentation, and chore/ for maintenance tasks.

Which merge strategy should I use for pull requests?▼

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

When should I choose GitFlow over GitHub Flow?▼

GitHub Flow suits most projects where main is always deployable and features merge via PR. GitFlow fits complex release cycles needing a develop branch and release branches, while trunk-based development works for CI/CD-heavy teams with short-lived branches.

Is force pushing to a shared branch ever acceptable?▼

Force push should never be used on main or master, and on shared feature branches it can destroy collaborators' references. If rewriting history is unavoidable, use --force-with-lease and confirm with the user first.

Related Skills

Explore More Software Engineering Skills→
Integra-BeautyIntegra-Beauty

integra-git-conventions

Enforce kebab-case branch names, conventional commits, and repository naming conventions.

Official
Intermediate
Veloxia-agencyVeloxia-agency

changelog-generator

Generate markdown or JSON changelog entries from Conventional Commit histories.

Community
Advanced
ladinglogichqladinglogichq

code-review

Automate structured code reviews with pytest and ruff checks.

Official
Advanced
hung-phanhung-phan

trunk-based-development

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

Community
Advanced