Git Workflow Standards

Conventional Commits, branch naming, and merge-strategy standards, with 7 reference docs.

Tested · Works

Test report

Verdict
Tested · Works
Score
9.2/10
Tested
Jul 14, 2026
Environment
Claude Code 2.x (agent harness)
Upstream re-checked
Aug 10, 2026 · edfcc9f

Asked for help before opening a PR from a one-commit branch named 'my-fix' with the message 'fixed stuff': the skill named the exact branch convention (bugfix/login-captcha-refresh), rewrote the commit to its own Conventional Commits worked example almost verbatim, and specified rebase-onto-develop per its own merge-strategy table — all more precise than generic advice, none of it wrong. (Listed here under our older name; the skill's own name is "Git Workflow Standards".)

Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works

  • Installs cleanly 5/5
  • Triggers reliably 5/5
  • Output vs. baseline 8/10
  • Docs & honesty 5/5

What Git Workflow Standards does

Defines concrete Git standards for a team: Conventional Commits format with a type table, a branch-naming/lifecycle table (feature/bugfix/hotfix/release), rebase-vs-merge rules, conflict-resolution steps, and PR/review templates, backed by 7 references/*.md deep-dive files bundled in the same folder (all confirmed present). Interactive git operations are advisory — it tells you the exact command, you run it. Triggers on requests to create a commit, manage branches, follow a git workflow, or handle merge conflicts.

How to install Git Workflow Standards

git clone https://github.com/Galaxy-Dawn/claude-scholar
cd claude-scholar
mkdir -p ~/.claude/skills
cp -r skills/git-workflow ~/.claude/skills/git-workflow

Skills live in ~/.claude/skills/ (global) or .claude/skills/ (per-project). Restart Claude Code after installing.

Commands — how to trigger Git Workflow Standards

  • /git-workflow Conventional Commits, branch naming, and merge-strategy standards, with 7 reference docs.

It also activates on plain-language prompts like these:

  • Write a conventional commit message for these changes
  • Suggest a clean branch name for this new feature
  • Help me clean up this messy commit history

Appears in

Frequently asked questions

Is the Git Workflow Standards skill free?
Yes. The skill itself is free from Galaxy-Dawn/claude-scholar. SkillProof publishes the install command and an independent test verdict at no cost.
Does Git Workflow Standards work with Claude Code?
We tested it with Claude Code 2.x (agent harness) on Jul 14, 2026. Verdict: Tested · Works. Asked for help before opening a PR from a one-commit branch named 'my-fix' with the message 'fixed stuff': the skill named the exact branch convention (bugfix/login-captcha-refresh), rewrote the commit to its own Conventional Commits worked example almost verbatim, and specified rebase-onto-develop per its own merge-strategy table — all more precise than generic advice, none of it wrong. (Listed here under our older name; the skill's own name is "Git Workflow Standards".)
What is the Git Workflow Standards SkillProof Score?
9.2/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 8/10, docs & honesty 5/5.
How do I install Git Workflow Standards?
Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
Can I use Git Workflow Standards with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.