Git Flow

Git Flow Best Practices (2026)

Workflow Choice

| Strategy | When | Verdict | |----------|------|---------| | Trunk-based (direct main) | Solo dev, prototypes, strong CI | OK if you have automated tests | | GitHub Flow (feature branch → PR → merge → delete) | Teams, OSS, code review | ✅ Default | | Git Flow (develop/release/hotfix) | Heavy release cycles | ❌ Outdated for most projects |

fuse-commit-pro default: GitHub Flow.

Branch Naming Convention

Format: / (kebab-case).

| Type | Use | Example | |------|-----|---------| | feat/ | New feature | feat/seo, feat/oauth-google | | fix/ | Bug fix | fix/sniper-loop, fix/csv-parser | | chore/ | Maintenance, deps | chore/bump-deps, chore/rename-files | | docs/ | Documentation | docs/api-reference | | refactor/ | Refactoring (no behavior change) | refactor/extract-utils | | perf/ | Performance | perf/db-indexes | | test/ | Tests only | test/auth-coverage | | ci/ | CI/CD config | ci/github-actions-cache | | build/ | Build system | build/vite-config | | style/ | Formatting | style/prettier-pass |

Rules:

• kebab-case only (no underscores, no spaces, no caps)
• # create

1. work + commit # multiple commits OK
2. git push -u origin feat/ # push with upstream
3. gh pr create # open PR
4. (review + CI)
5. gh pr merge --squash --delete-branch # merge + cleanup

**Keep branches short-lived** (` (automatic if `--delete-branch` used remotely)

## Pull Request Template

```markdown
## Summary

## Changes

## Test plan
- [ ] Manual test on X
- [ ] CI green
- [ ] Sniper validation clean

## Breaking changes
None / 

Anti-Patterns

• ❌ Long-lived feature branches (> 1 week) — rebase early or split
• ❌ Commits on main "to save time" — bypasses review, breaks CI gates
• ❌ Force push to main — never. Forbidden in fuse-commit-pro.
• ❌ Branch named wip, temp, test123 — meaningless, can't be found later
• ❌ PR without description — reviewers can't context-switch
• ❌ Merging your own PR without review (when working in a team)
• ❌ Stale branches (no commits > 30 days) — delete or close

Solo Dev Mode

If you're alone on a repo with no PR review:

• Still use feature branches (rollback safety net)
• Self-PR is fine for sanity check (you'll see the diff fresh)
• Or commit-then-push on main with strong CI as safety
• fuse-commit-pro:commit detects no-remote case and skips Step 7

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: fusengine
• Source: fusengine/agents
• License: MIT

Install and usage instructions live in the source repository linked above.