How do I install the Moai Foundation Git skill?

Run npx skillmds add majiayu000/moai-foundation-git in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Moai Foundation Git skill do?

Git workflows, branching strategies, and commit conventions It is listed under Coding & Dev Tools on SkillMD.

Is Moai Foundation Git safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Moai Foundation Git?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Moai Foundation Git free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Moai Foundation Git?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Moai Foundation Git by majiayu000 — Agent Skill

Name: Moai Foundation Git
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Git Workflow Expert

Version Control Best Practices

Focus: Branching Strategy, Commit Conventions, PR Workflow
Standards: Conventional Commits, Semantic Versioning

Overview

Production-grade Git workflows for team collaboration.

Core Concepts

Branching Strategy: Feature branches, trunk-based development
Commit Messages: Conventional commits format
PR Process: Code review, CI/CD integration

Branching Strategies

Git Flow (Enterprise)

main (production)
  ├── develop (integration)
  │   ├── feature/user-auth
  │   ├── feature/payment
  │   └── release/v1.2.0
  └── hotfix/critical-bug

Trunk-Based Development (Modern)

main (always deployable)
  ├── feature/short-lived-branch-1
  └── feature/short-lived-branch-2

Recommendation: Trunk-based for small teams (<10), Git Flow for larger teams.

Commit Conventions

Conventional Commits Format

<type>(<scope>): <subject>

<body>

<footer>

Types

feat: New feature
fix: Bug fix
docs: Documentation only
style: Formatting (no code change)
refactor: Code restructuring
test: Adding tests
chore: Build/config changes

Examples

# Feature
git commit -m "feat(auth): add JWT authentication

Implements OAuth 2.0 flow with refresh tokens.
Closes #123"

# Bug fix
git commit -m "fix(api): handle null response

Prevents crashes when API returns empty data.
Fixes #456"

# Breaking change
git commit -m "feat(api)!: change response format

BREAKING CHANGE: API now returns {data, meta} instead of raw array"

PR Workflow

1. Create Feature Branch

git checkout -b feature/user-profile

2. Make Changes & Commit

git add .
git commit -m "feat(profile): add user profile page"

3. Push & Create PR

git push -u origin feature/user-profile
# Create PR on GitHub/GitLab

4. Code Review

✅ CI/CD passes
✅ Tests added
✅ Documentation updated
✅ 1+ approvals

5. Merge

# Squash merge (clean history)
git merge --squash feature/user-profile

# Or rebase (preserve commits)
git rebase main

Best Practices

Small Commits: One logical change per commit
Descriptive Messages: Explain why, not just what
Atomic Commits: Each commit should leave code in working state
Linear History: Use rebase to avoid merge commits
Protected Branches: Require PR reviews for main

Validation Checklist

Branch: Feature branch created from main?
Commits: Follow conventional format?
Tests: All tests passing?
Review: PR approved by team?
CI/CD: All checks passed?

Related Skills

moai-core-rules: Development workflow
moai-devops-ci: CI/CD integration

Last Updated: 2025-11-20

---name: moai-foundation-gitdescription: Git workflows, branching strategies, and commit conventions--- # Git Workflow Expert **Version Control Best Practices** > **Focus**: Branching Strategy, Commit Conventions, PR Workflow > **Standards**: Conventional Commits, Semantic Versioning --- ## Overview Production-grade Git workflows for team collaboration. ### Core Concepts 1. **Branching Strategy**: Feature branches, trunk-based development 2. **Commit Messages**: Conventional commits format 3. **PR Process**: Code review, CI/CD integration --- ## Branching Strategies ### Git Flow (Enterprise) ``` main (production) ├── develop (integration) │ ├── feature/user-auth │ ├── feature/payment │ └── release/v1.2.0 └── hotfix/critical-bug ``` ### Trunk-Based Development (Modern) ``` main (always deployable) ├── feature/short-lived-branch-1 └── feature/short-lived-branch-2 ``` **Recommendation**: Trunk-based for small teams (<10), Git Flow for larger teams. --- ## Commit Conventions ### Conventional Commits Format ``` <type>(<scope>): <subject> <body> <footer> ``` ### Types - **feat**: New feature - **fix**: Bug fix - **docs**: Documentation only - **style**: Formatting (no code change) - **refactor**: Code restructuring - **test**: Adding tests - **chore**: Build/config changes ### Examples ```bash # Feature git commit -m "feat(auth): add JWT authentication Implements OAuth 2.0 flow with refresh tokens. Closes #123" # Bug fix git commit -m "fix(api): handle null response Prevents crashes when API returns empty data. Fixes #456" # Breaking change git commit -m "feat(api)!: change response format BREAKING CHANGE: API now returns {data, meta} instead of raw array" ``` --- ## PR Workflow ### 1. Create Feature Branch ```bash git checkout -b feature/user-profile ``` ### 2. Make Changes & Commit ```bash git add . git commit -m "feat(profile): add user profile page" ``` ### 3. Push & Create PR ```bash git push -u origin feature/user-profile # Create PR on GitHub/GitLab ``` ### 4. Code Review - ✅ CI/CD passes - ✅ Tests added - ✅ Documentation updated - ✅ 1+ approvals ### 5. Merge ```bash # Squash merge (clean history) git merge --squash feature/user-profile # Or rebase (preserve commits) git rebase main ``` --- ## Best Practices 1. **Small Commits**: One logical change per commit 2. **Descriptive Messages**: Explain _why_, not just _what_ 3. **Atomic Commits**: Each commit should leave code in working state 4. **Linear History**: Use rebase to avoid merge commits 5. **Protected Branches**: Require PR reviews for `main` --- ## Validation Checklist - [ ] **Branch**: Feature branch created from `main`? - [ ] **Commits**: Follow conventional format? - [ ] **Tests**: All tests passing? - [ ] **Review**: PR approved by team? - [ ] **CI/CD**: All checks passed? --- ## Related Skills - `moai-core-rules`: Development workflow - `moai-devops-ci`: CI/CD integration --- **Last Updated**: 2025-11-20

Frequently asked questions