Agent skill

Moai Ref Git Workflow

by modu-ai in modu-ai/moai-adk

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

Apache-2.0Auto-check passedDevelopment

Install Moai Ref Git Workflow

skills CLI
$ npx skills add modu-ai/moai-adk --skill moai-ref-git-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install modu-ai/moai-adk moai-ref-git-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/modu-ai/moai-adk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/moai-ref-git-workflow .claude/skills/moai-ref-git-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
moai-ref-git-workflow
GitHub stars
1.2k
Token cost
~1.8k tokens
SKILL.md length
534 words
Files
1
Skills in repo
48
Repo updated
First seen
Licence
Apache-2.0

At a glance

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

  • Tasks that involve Git workflow
  • SKILL.md covers Target Agent, Branch Strategy Patterns, Branch Naming Convention and Conventional Commits Reference, plus 7 more sections
  • Calls git and gh
  • Tasks that involve Commit messages

What it does

Moai Ref Git Workflow is an agent skill from modu-ai/moai-adk. Git workflow patterns, branch strategies, conventional commits, and PR templates reference for git operations. Agent-extending skill that amplifies manager-git expertise with production-grade git workflow patterns. NOT for: code implementation, testing, architecture design, documentation content.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git workflow and Commit messages. It works with Git. The repository describes itself as: Agentic development harness for Claude Code — SPEC-driven plan/run/sync, TRUST 5 quality gates, model+effort routing, and Claude×GLM multi-LLM cost control. Single Go binary, 16… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Git workflow
  • Tasks that involve Commit messages

Example prompts

  • “/moai-ref-git-workflow”

What it can do on your machine

Read from SKILL.md and the folder at commit 6c55321. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Moai Ref Git Workflow loads about 1.8k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 534 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from modu-ai/moai-adk at commit 6c55321, republished under its Apache-2.0 licence (© modu-ai). 534 words, ~1,752 tokens.

Download SKILL.mdSave it as .claude/skills/moai-ref-git-workflow/SKILL.md (or your agent's skills folder).
name
moai-ref-git-workflow
description
Git workflow patterns, branch strategies, conventional commits, and PR templates reference for git operations. Agent-extending skill that amplifies manager-git expertise with production-grade git workflow patterns. NOT for: code implementation, testing, architecture design, documentation content.
when_to_use
Use for git workflow reference: branch strategies, conventional commits, PR templates, merge and rebase flows, and commit/branch/release conventions…
user-invocable
false
metadata.version
1.0.0
metadata.category
workflow
metadata.status
active
metadata.updated
2026-03-30
metadata.tags
git, branch, commit, pr, workflow, reference
progressive_disclosure.enabled
true
progressive_disclosure.level1_tokens
100
progressive_disclosure.level2_tokens
3000

Git Workflow Reference

Target Agent

manager-git - Applies these patterns directly to git operations, branch management, and PR creation.

Branch Strategy Patterns

GitHub Flow (Default for Most Projects)
main ─────────────────────────────────────────
  └── feat/SPEC-XXX-description ──── PR ──→ merge

Rules:

  • main is always deployable
  • Feature branches from main
  • PR required for all merges
  • Delete branch after merge
GitFlow (Complex Release Cycles)
main ──────────────────────────────────────────
  └── develop ─────────────────────────────────
        ├── feature/SPEC-XXX ──── PR ──→ develop
        └── release/v1.2.0 ────── PR ──→ main + develop
Trunk-Based (CI/CD Heavy)
main ──────────────────────────────────────────
  └── short-lived branch (< 1 day) ──→ merge

Branch Naming Convention

PatternExampleUse Case
feat/SPEC-{ID}-{slug}feat/SPEC-AUTH-001-jwt-authNew feature
fix/SPEC-{ID}-{slug}fix/SPEC-BUG-042-null-checkBug fix
refactor/{slug}refactor/extract-auth-middlewareRefactoring
docs/{slug}docs/api-reference-updateDocumentation
chore/{slug}chore/upgrade-dependenciesMaintenance

Conventional Commits Reference

TypeWhenExample
featNew featurefeat(auth): add JWT refresh token flow
fixBug fixfix(api): handle null user in profile endpoint
refactorCode restructurerefactor(db): extract query builder
testTest changestest(auth): add login edge case tests
docsDocumentationdocs(api): update endpoint descriptions
choreMaintenancechore(deps): upgrade Go to 1.23
perfPerformanceperf(query): add index for user lookup
styleFormattingstyle: apply gofmt formatting
ciCI/CD changesci: add GitHub Actions workflow
revertRevert commitrevert: undo feat(auth) commit abc123
Commit Message Structure
<type>(<scope>): <description>    # max 72 chars

[optional body]                    # what and why, not how

[optional footer]                  # Breaking changes, issue refs
BREAKING CHANGE: <description>
Refs: #123, SPEC-AUTH-001

Pull Request Template

markdown
## Summary
- [1-3 bullet points describing what this PR does]

## Changes
- [ ] File 1: description of change
- [ ] File 2: description of change

## Test Plan
- [ ] Unit tests added/updated
- [ ] Integration tests pass
- [ ] Manual testing completed

## SPEC Reference
- SPEC-{ID}: {title}

## Checklist
- [ ] Tests pass (project test command)
- [ ] Lint and format pass (project toolchain)
- [ ] No secrets committed
- [ ] Documentation updated if needed

Merge Strategy Selection

StrategyWhenCommand
Squash mergeFeature branches (clean history)gh pr merge --squash
Merge commitRelease branches (preserve history)gh pr merge --merge
RebaseSmall, clean commitsgh pr merge --rebase

The active method for sync-phase PR auto-merge is governed by the git_strategy.<mode>.merge_method config value (squash | merge | rebase; default squash), not hardcoded. The sync agent resolves it from the active mode profile and renders the matching gh pr merge --<merge_method> command.

Git Safety Rules

ActionRiskRule
git push --forceOverwrites remoteNEVER on main/master, ask user first
git reset --hardLoses local changesConfirm with user first
git checkout .Discards changesConfirm with user first
git branch -DDeletes branchOnly after merge confirmed
--no-verifySkips hooksNEVER unless user explicitly requests
git rebase -iInteractive (not supported)NEVER use (requires interactive input)

Context Memory in Commits

Embed decision context in commit messages for future session continuity:

feat(auth): implement JWT refresh token rotation

Decision: Chose rotation over sliding window for security
Pattern: Middleware chain: RateLimit -> Auth -> Authz -> Handler
Gotcha: Token blacklist requires Redis, not just in-memory cache

Refs: SPEC-AUTH-001
<!-- moai:evolvable-start id="rationalizations" -->
Show full SKILL.md (224 more words)Show less

Common Rationalizations

RationalizationReality
"I will clean up the commit messages before merging"Interactive rebase is error-prone under pressure. Write clean commits from the start.
"Force push is fine on my feature branch"Collaborators or CI may have fetched the branch. Force push destroys their reference. Use --force-with-lease.
"This commit is too small to need a conventional format"Changelog generators, bisect, and blame all depend on consistent commit formats. Every commit matters.
"I will push directly to main, it is a small fix"Direct pushes bypass code review and CI. Even small fixes can break production.
"Merge commits are messy, I always squash"Squash loses individual commit context. Merge commits preserve the development narrative for future debugging.
<!-- moai:evolvable-end -->
<!-- moai:evolvable-start id="red-flags" -->

Red Flags

  • Commit message does not follow conventional format (type(scope): description)
  • Force push to main or shared release branch
  • PR merged without CI passing
  • Branch name does not indicate feature, fix, or SPEC reference
  • Merge conflict markers found in committed files
<!-- moai:evolvable-end -->
<!-- moai:evolvable-start id="verification" -->

Verification

  • All commit messages follow conventional format (show git log --oneline)
  • Branch name follows convention (feat/, fix/, refactor/, docs/, chore/ prefix)
  • No force pushes to main or protected branches (check reflog or CI)
  • PR has passing CI checks before merge
  • No merge conflict markers in committed files (grep for <<<<<<<)
  • SPEC-ID referenced in commit message or PR description when applicable
<!-- moai:evolvable-end -->

© modu-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/moai-ref-git-workflow of modu-ai/moai-adk.

Open the folder on GitHubat commit 6c55321

Compare with similar skills

Moai Ref Git Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Moai Ref Git Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Moai Ref Git Workflow this skillmodu-ai/moai-adk1.2k—~1.8kAutomated safety check: PassApache-2.0
ToolJet Multi-Repo CommitToolJet/ToolJet41k—~1.3kAutomated safety check: PassAGPL-3.0
Git Workflow and Versioningaddyosmani/agent-skills102k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Saleor Commit Workflowsaleor/saleor23k—~575Automated safety check: PassBSD-3-Clause
Emoji Commit ConventionsbaptisteArno/typebot.io11k—~424Automated safety check: PassCustom licence

Similar skills

  • Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.

    41k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    102k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes
  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.

    23k GitHub stars~575 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Emoji Commit Conventions

    baptisteArno/typebot.io

    Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.

    11k GitHub stars~424 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Draft Pull Request Creator

    wordpress-mobile/WordPress-Android

    Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.

    3.2k GitHub stars~881 tokensUpdated yesterday
    DevelopmentAuto-check: notes

More from modu-ai/moai-adk

All 48 skills in this repo
  • Builds hand-editable SVG diagrams from computed layout coordinates, lints the source and renders a 2x PNG, with rules for when mermaid is the better choice.

    1.2k GitHub stars~5.2k tokensUpdated today
    Auto-check: notes
  • MoAI Foundation Core

    modu-ai/moai-adk

    Reference for MoAI-ADK's core development principles: TRUST 5 quality gates, SPEC-first domain-driven workflow, agent delegation and token budgeting.

    1.2k GitHub stars~5k tokensUpdated today
    Auto-check passed
  • MoAI SPEC Workflow

    modu-ai/moai-adk

    Manages SPEC documents for MoAI-ADK development, with GEARS or EARS requirement notation, acceptance criteria and a link into the Plan-Run-Sync workflow.

    1.2k GitHub stars~5.1k tokensUpdated today
    Auto-check passed
  • MoAI TDD Workflow

    modu-ai/moai-adk

    Drives test-first development through the RED, GREEN, REFACTOR cycle, with a config switch that selects between TDD and a DDD workflow for existing code.

    1.2k GitHub stars~3.1k tokensUpdated today
    Auto-check passed
  • MoAI Worktree Management

    modu-ai/moai-adk

    Gives each SPEC its own Git worktree with a registry of active workspaces, base-branch sync and cleanup of merged ones, inside the MoAI-ADK workflow.

    1.2k GitHub stars~3.9k tokensUpdated today
    Auto-check passed
  • Watches a pull request's CI checks after creation, separates required from auxiliary failures, applies limited safe fixes and escalates anything semantic to you.

    1.2k GitHub stars~2.4k tokensUpdated today
    Auto-check: notes

Works with

Categories

Questions about Moai Ref Git Workflow

What does Moai Ref Git Workflow do?

Git workflow patterns, branch strategies, conventional commits, and PR templates reference for git operations. Moai Ref Git Workflow is an agent skill from modu-ai/moai-adk. Git workflow patterns, branch strategies, conventional commits, and PR templates reference for git operations.

When should I use Moai Ref Git Workflow?

Moai Ref Git Workflow fits situations like: tasks that involve Git workflow; tasks that involve Commit messages.

How do I install Moai Ref Git Workflow in Claude Code?

Run `npx skills add modu-ai/moai-adk --skill moai-ref-git-workflow -a claude-code`. Or copy the skill folder (.claude/skills/moai-ref-git-workflow in modu-ai/moai-adk) into .claude/skills/moai-ref-git-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Moai Ref Git Workflow in Codex?

Run `npx skills add modu-ai/moai-adk --skill moai-ref-git-workflow -a codex`. Or copy the skill folder (.claude/skills/moai-ref-git-workflow in modu-ai/moai-adk) into .agents/skills/moai-ref-git-workflow in your project. Codex loads it when a task matches its description.

Can I use Moai Ref Git Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add modu-ai/moai-adk --skill moai-ref-git-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/moai-ref-git-workflow, .gemini/skills/moai-ref-git-workflow, .github/skills/moai-ref-git-workflow and .opencode/skills/moai-ref-git-workflow in your project.

What does Moai Ref Git Workflow need to run?

Going by SKILL.md and its folder, Moai Ref Git Workflow needs the command-line tools its instructions call (git and gh).

Does Moai Ref Git Workflow access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Moai Ref Git Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Moai Ref Git Workflow use?

Moai Ref Git Workflow is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Moai Ref Git Workflow use?

About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Moai Ref Git Workflow?

Skills that share tags, products or a category with Moai Ref Git Workflow: ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 102k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars) and Saleor Commit Workflow (saleor/saleor, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Moai Ref Git Workflow?

modu-ai (a GitHub organization) maintains it in modu-ai/moai-adk, which has 1,230 GitHub stars. The repository holds 48 skills in this directory. The repository was last updated on October 7, 2026.

Source: modu-ai/moai-adk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.