How do I install the Git Workflow skill?

Run npx skillmds@latest add irahardianto/git-workflow-3 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.

Is Git Workflow safe to use?

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

Which AI agents work with Git Workflow?

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 Git Workflow free to use?

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

Who published Git Workflow?

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

Git Workflow by irahardianto — Agent Skill

Name: Git Workflow
Rating: 4.2 (5 reviews)
Author: irahardianto

File contents

Git Workflow Principles

Commit Messages — Conventional Commits

Format:

<type>(<scope>): <description>

[optional body]

[optional footer]

Types:

Type	Purpose
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation only
`style`	Formatting, semicolons, etc.
`refactor`	Code change (no new feature/fix)
`test`	Adding or updating tests
`chore`	Maintenance, dependencies
`perf`	Performance improvement
`ci`	CI/CD configuration changes

Rules:

Description is imperative mood ("add" not "added", "fix" not "fixes")
Scope matches the feature area (e.g., task, auth, ui)
Description is concise (<72 characters)
Body explains why, not what (the diff shows what)

Branch Naming

Format: <type>/<ticket-or-short-description>

Examples:

feat/task-crud-api
fix/auth-token-expiry
refactor/storage-layer
chore/update-deps

Rules:

Use lowercase with hyphens (kebab-case)
Prefix matches commit type
Keep branch names short but descriptive

Commit Hygiene

One logical change per commit — don't mix unrelated changes
Never commit broken tests — all tests must pass before committing
Don't commit debug code — remove console.log, print statements, TODO hacks
Don't commit secrets — use .gitignore and environment variables

PR Size Guidelines

Ideal: <400 lines changed
Acceptable: 400-800 lines
Too large: >800 lines — split into smaller PRs

Why: Large PRs get rubber-stamped. Small PRs get thoughtful reviews.

Merge Strategy

Feature branches → main: Squash merge (clean history)
Release branches: Merge commit (preserve history)
Hotfixes: Cherry-pick to affected branches

Git Workflow Checklist

Branch named with correct type prefix?
All commits follow conventional format?
No debug code or secrets committed?
All tests pass before committing?
PR is <400 lines (or justified if larger)?
Commit messages explain why, not just what?

Related Principles

Code Completion Mandate @.claude/rules/code-completion-mandate.md
Testing Strategy @.claude/rules/testing-strategy.md
Security Mandate @.claude/rules/security-mandate.md

---name: git-workflow-3description: Apply git workflow conventions when creating branches, writing commit messages, managing pull requests, or resolving merge conflicts. Covers conventional commits, branch naming, PR hygiene, and release tagging.---## Git Workflow Principles### Commit Messages — Conventional Commits**Format:**```<type>(<scope>): <description>[optional body][optional footer]```**Types:**| Type | Purpose || ---------- | -------------------------------- || `feat` | New feature || `fix` | Bug fix || `docs` | Documentation only || `style` | Formatting, semicolons, etc. || `refactor` | Code change (no new feature/fix) || `test` | Adding or updating tests || `chore` | Maintenance, dependencies || `perf` | Performance improvement || `ci` | CI/CD configuration changes |**Rules:**- Description is imperative mood ("add" not "added", "fix" not "fixes")- Scope matches the feature area (e.g., `task`, `auth`, `ui`)- Description is concise (<72 characters)- Body explains **why**, not what (the diff shows what)### Branch Naming**Format:** `<type>/<ticket-or-short-description>`**Examples:**```feat/task-crud-apifix/auth-token-expiryrefactor/storage-layerchore/update-deps```**Rules:**- Use lowercase with hyphens (kebab-case)- Prefix matches commit type- Keep branch names short but descriptive### Commit Hygiene- **One logical change per commit** — don't mix unrelated changes- **Never commit broken tests** — all tests must pass before committing- **Don't commit debug code** — remove console.log, print statements, TODO hacks- **Don't commit secrets** — use `.gitignore` and environment variables### PR Size Guidelines- **Ideal:** <400 lines changed- **Acceptable:** 400-800 lines- **Too large:** >800 lines — split into smaller PRs**Why:** Large PRs get rubber-stamped. Small PRs get thoughtful reviews.### Merge Strategy- **Feature branches → main:** Squash merge (clean history)- **Release branches:** Merge commit (preserve history)- **Hotfixes:** Cherry-pick to affected branches### Git Workflow Checklist- [ ] Branch named with correct type prefix?- [ ] All commits follow conventional format?- [ ] No debug code or secrets committed?- [ ] All tests pass before committing?- [ ] PR is <400 lines (or justified if larger)?- [ ] Commit messages explain why, not just what?### Related Principles- Code Completion Mandate @.claude/rules/code-completion-mandate.md- Testing Strategy @.claude/rules/testing-strategy.md- Security Mandate @.claude/rules/security-mandate.md

Frequently asked questions

Git Workflow