File contents Git Workflow Principles
Commit Messages — Conventional Commits
Format:
<type>(<scope>): <description>
[optional body]
[optional footer]
Types:
Type
Purpose
featNew feature
fixBug fix
docsDocumentation only
styleFormatting, semicolons, etc.
refactorCode change (no new feature/fix)
testAdding or updating tests
choreMaintenance, dependencies
perfPerformance improvement
ciCI/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 changesNever commit broken tests — all tests must pass before committingDon't commit debug code — remove console.log, print statements, TODO hacksDon't commit secrets — use .gitignore and environment variables
PR Size Guidelines
Ideal: <400 lines changedAcceptable: 400-800 linesToo 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
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
Source: irahardianto/claude-superpowers — distributed by TomeVault .
1 --- 2 name: irahardianto-claude-superpowers-git-workflow 3 description: Git Workflow Principles 4 --- 5 6 ## Git Workflow Principles 7 8 ### Commit Messages — Conventional Commits 9 10 **Format:** 11 ``` 12 <type>(<scope>): <description> 13 14 [optional body] 15 16 [optional footer] 17 ``` 18 19 **Types:** 20 | Type | Purpose | 21 | ---------- | -------------------------------- | 22 | `feat` | New feature | 23 | `fix` | Bug fix | 24 | `docs` | Documentation only | 25 | `style` | Formatting, semicolons, etc. | 26 | `refactor` | Code change (no new feature/fix) | 27 | `test` | Adding or updating tests | 28 | `chore` | Maintenance, dependencies | 29 | `perf` | Performance improvement | 30 | `ci` | CI/CD configuration changes | 31 32 **Rules:** 33 - Description is imperative mood ("add" not "added", "fix" not "fixes") 34 - Scope matches the feature area (e.g., `task`, `auth`, `ui`) 35 - Description is concise (<72 characters) 36 - Body explains **why**, not what (the diff shows what) 37 38 ### Branch Naming 39 40 **Format:** `<type>/<ticket-or-short-description>` 41 42 **Examples:** 43 ``` 44 feat/task-crud-api 45 fix/auth-token-expiry 46 refactor/storage-layer 47 chore/update-deps 48 ``` 49 50 **Rules:** 51 - Use lowercase with hyphens (kebab-case) 52 - Prefix matches commit type 53 - Keep branch names short but descriptive 54 55 ### Commit Hygiene 56 57 - **One logical change per commit** — don't mix unrelated changes 58 - **Never commit broken tests** — all tests must pass before committing 59 - **Don't commit debug code** — remove console.log, print statements, TODO hacks 60 - **Don't commit secrets** — use `.gitignore` and environment variables 61 62 ### PR Size Guidelines 63 64 - **Ideal:** <400 lines changed 65 - **Acceptable:** 400-800 lines 66 - **Too large:** >800 lines — split into smaller PRs 67 68 **Why:** Large PRs get rubber-stamped. Small PRs get thoughtful reviews. 69 70 ### Merge Strategy 71 72 - **Feature branches → main:** Squash merge (clean history) 73 - **Release branches:** Merge commit (preserve history) 74 - **Hotfixes:** Cherry-pick to affected branches 75 76 ### Git Workflow Checklist 77 78 - [ ] Branch named with correct type prefix? 79 - [ ] All commits follow conventional format? 80 - [ ] No debug code or secrets committed? 81 - [ ] All tests pass before committing? 82 - [ ] PR is <400 lines (or justified if larger)? 83 - [ ] Commit messages explain why, not just what? 84 85 ### Related Principles 86 - Code Completion Mandate @.claude/rules/code-completion-mandate.md 87 - Testing Strategy @.claude/rules/testing-strategy.md 88 - Security Mandate @.claude/rules/security-mandate.md 89 90 --- 91 > Source: [irahardianto/claude-superpowers](https://github.com/irahardianto/claude-superpowers) — distributed by [TomeVault](https://tomevault.io). 92 <!-- tomevault:4.0:skill_md:2026-06-16 -->
commit 619275e03b
Frequently asked questions How do I install the Irahardianto Claude Superpowers Git Workflow skill? Run npx skillmds@latest add tomevault-io/irahardianto-claude-superpowers-git-workflow 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 Irahardianto Claude Superpowers Git Workflow skill do? Git Workflow Principles It is listed under Productivity on SkillMD.
Is Irahardianto Claude Superpowers Git Workflow safe to use? This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
Which AI agents work with Irahardianto Claude Superpowers 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 Irahardianto Claude Superpowers Git Workflow free to use? Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
Who published Irahardianto Claude Superpowers Git Workflow? tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.
tomevault-io