Git Workflow
Covers branching strategies, conventional commits, CI/CD automation, repository hygiene, and git internals. GitHub CLI usage is handled by a separate github-cli skill; this skill focuses on git workflow patterns and CI/CD configuration.
Quick Reference
| Area |
Key Practice |
| Branching |
Trunk-based development with short-lived feature branches |
| Commits |
Conventional commits with imperative mood |
| History |
Linear history via rebase; squash noisy commits |
| PRs |
Small, stacked changes; no mega PRs |
| Main branch |
Always deployable; broken main is an emergency |
| CI/CD |
Modular GitHub Actions with reusable workflows |
| Merging |
Green CI + review required before merge |
| Versioning |
Semantic Release or Changesets (never manual) |
| Branches |
Max 48 hours lifespan; auto-prune stale/merged |
| Secrets |
OIDC Connect in pipelines; never hardcode tokens |
| Signing |
Sign commits with SSH or GPG keys for verified authorship |
Branch Naming
| Type |
Use For |
Example |
| feat |
New features |
feat/add-user-auth |
| fix |
Bug fixes |
fix/login-redirect |
| chore |
Maintenance |
chore/update-deps |
| docs |
Documentation |
docs/api-reference |
| refactor |
Code restructuring |
refactor/auth-module |
Conventional Commit Types
| Type |
Purpose |
Version Bump |
feat |
New features |
Minor |
fix |
Bug fixes |
Patch |
docs |
Documentation only |
None |
style |
Formatting, no logic changes |
None |
refactor |
Neither fix nor feature |
None |
perf |
Performance improvements |
Patch |
test |
Adding or correcting tests |
None |
build |
Build system or external dependencies |
None |
ci |
CI configuration changes |
None |
chore |
Tooling, maintenance, non-src changes |
None |
revert |
Revert a previous commit |
Varies |
Append ! after type/scope for breaking changes (major version bump).
Pre-Merge Checks
All PRs require before merge:
- Lint
- Type check
- Tests
- Security scan
- Review approval (human or automated)
Auto-merge is acceptable for low-risk PRs when pipeline succeeds.
Troubleshooting
| Issue |
Resolution |
| Merge conflicts on long-running branch |
Rebase onto main frequently; break remaining work into new branch if over 48 hours |
| Broken main branch |
Treat as emergency; revert offending commit, then fix forward on a branch |
| Lost commits or data recovery |
Use git reflog and object inspection (git cat-file, git fsck) |
| CI pipeline failures |
Check reusable workflow versions; verify OIDC permissions |
| Stacked PR conflicts after rebase |
Restack entire chain from base; Graphite handles automatically with gt restack |
| Large file accidentally committed |
Use git filter-repo to remove from history (not git filter-branch) |
Common Mistakes
| Mistake |
Correct Pattern |
| Keeping feature branches alive longer than 48 hours |
Merge or rebase daily; break large work into stacked PRs |
| Committing directly to main without branch protection |
Enable branch protection rules requiring CI and review |
| Using merge commits that clutter history |
Rebase and squash to maintain linear history |
| Hardcoding tokens in GitHub Actions workflows |
Use OIDC Connect for authentication in CI/CD pipelines |
| Creating monolithic CI workflows in a single file |
Split into reusable workflows and composite actions |
Fix bug as commit message |
fix(scope): correct bug description (conventional) |
feat: Added feature (past tense) |
feat: add feature (imperative mood, lowercase) |
Using git filter-branch for history rewriting |
Use git filter-repo (faster, safer, officially recommended) |
| Pushing to main directly |
Create feature branch first |
| Unsigned commits in shared repositories |
Configure commit signing with SSH or GPG keys |
Delegation
- Audit repository branch hygiene and stale branches: Use
Explore agent to list and classify branch age and merge status
- Set up CI/CD pipelines with reusable workflows: Use
Task agent to create modular GitHub Actions configurations
- Design branching strategy for a new project: Use
Plan agent to evaluate trunk-based vs Git Flow based on team needs
References
- branching-strategies.md -- Git Flow, GitHub Flow, GitLab Flow, One-Flow comparison and selection criteria
- trunk-based-development.md -- Core principles, workflow steps, feature flags, and anti-patterns
- stacked-changes.md -- Stacked PRs concept, manual stacking, Graphite automation, best practices
- conventional-commits.md -- Commit format, types, scopes, breaking changes, and full workflow
- github-actions.md -- Reusable workflows, matrix testing, deployment environments, security
- git-internals.md -- Object model, SHA hashing, index, references, packfiles, garbage collection
- automation-scripts.md -- Branch pruning, semantic release, security scanning, stacked PR helpers
- issue-templates.md -- Bug report, feature request, task, and minimal issue templates
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: git-workflow-1243description: Designs git workflows covering branching strategies, trunk-based development, stacked changes, conventional commits, CI/CD pipelines, and repository hygiene. Use when setting up branching models, writing commit messages, configuring GitHub Actions, managing stacked PRs, cleaning stale branches, creating issue templates, or recovering lost commits. Use when this capability is needed.4---56# Git Workflow78Covers branching strategies, conventional commits, CI/CD automation, repository hygiene, and git internals. GitHub CLI usage is handled by a separate `github-cli` skill; this skill focuses on git workflow patterns and CI/CD configuration.910## Quick Reference1112| Area | Key Practice |13| ----------- | --------------------------------------------------------- |14| Branching | Trunk-based development with short-lived feature branches |15| Commits | Conventional commits with imperative mood |16| History | Linear history via rebase; squash noisy commits |17| PRs | Small, stacked changes; no mega PRs |18| Main branch | Always deployable; broken main is an emergency |19| CI/CD | Modular GitHub Actions with reusable workflows |20| Merging | Green CI + review required before merge |21| Versioning | Semantic Release or Changesets (never manual) |22| Branches | Max 48 hours lifespan; auto-prune stale/merged |23| Secrets | OIDC Connect in pipelines; never hardcode tokens |24| Signing | Sign commits with SSH or GPG keys for verified authorship |2526## Branch Naming2728| Type | Use For | Example |29| -------- | ------------------ | ---------------------- |30| feat | New features | `feat/add-user-auth` |31| fix | Bug fixes | `fix/login-redirect` |32| chore | Maintenance | `chore/update-deps` |33| docs | Documentation | `docs/api-reference` |34| refactor | Code restructuring | `refactor/auth-module` |3536## Conventional Commit Types3738| Type | Purpose | Version Bump |39| ---------- | ------------------------------------- | ------------ |40| `feat` | New features | Minor |41| `fix` | Bug fixes | Patch |42| `docs` | Documentation only | None |43| `style` | Formatting, no logic changes | None |44| `refactor` | Neither fix nor feature | None |45| `perf` | Performance improvements | Patch |46| `test` | Adding or correcting tests | None |47| `build` | Build system or external dependencies | None |48| `ci` | CI configuration changes | None |49| `chore` | Tooling, maintenance, non-src changes | None |50| `revert` | Revert a previous commit | Varies |5152Append `!` after type/scope for breaking changes (major version bump).5354## Pre-Merge Checks5556All PRs require before merge:5758- Lint59- Type check60- Tests61- Security scan62- Review approval (human or automated)6364Auto-merge is acceptable for low-risk PRs when pipeline succeeds.6566## Troubleshooting6768| Issue | Resolution |69| -------------------------------------- | ---------------------------------------------------------------------------------- |70| Merge conflicts on long-running branch | Rebase onto main frequently; break remaining work into new branch if over 48 hours |71| Broken main branch | Treat as emergency; revert offending commit, then fix forward on a branch |72| Lost commits or data recovery | Use git reflog and object inspection (`git cat-file`, `git fsck`) |73| CI pipeline failures | Check reusable workflow versions; verify OIDC permissions |74| Stacked PR conflicts after rebase | Restack entire chain from base; Graphite handles automatically with `gt restack` |75| Large file accidentally committed | Use `git filter-repo` to remove from history (not `git filter-branch`) |7677## Common Mistakes7879| Mistake | Correct Pattern |80| ----------------------------------------------------- | ------------------------------------------------------------- |81| Keeping feature branches alive longer than 48 hours | Merge or rebase daily; break large work into stacked PRs |82| Committing directly to main without branch protection | Enable branch protection rules requiring CI and review |83| Using merge commits that clutter history | Rebase and squash to maintain linear history |84| Hardcoding tokens in GitHub Actions workflows | Use OIDC Connect for authentication in CI/CD pipelines |85| Creating monolithic CI workflows in a single file | Split into reusable workflows and composite actions |86| `Fix bug` as commit message | `fix(scope): correct bug description` (conventional) |87| `feat: Added feature` (past tense) | `feat: add feature` (imperative mood, lowercase) |88| Using `git filter-branch` for history rewriting | Use `git filter-repo` (faster, safer, officially recommended) |89| Pushing to main directly | Create feature branch first |90| Unsigned commits in shared repositories | Configure commit signing with SSH or GPG keys |9192## Delegation9394- **Audit repository branch hygiene and stale branches**: Use `Explore` agent to list and classify branch age and merge status95- **Set up CI/CD pipelines with reusable workflows**: Use `Task` agent to create modular GitHub Actions configurations96- **Design branching strategy for a new project**: Use `Plan` agent to evaluate trunk-based vs Git Flow based on team needs9798## References99100- [branching-strategies.md](references/branching-strategies.md) -- Git Flow, GitHub Flow, GitLab Flow, One-Flow comparison and selection criteria101- [trunk-based-development.md](references/trunk-based-development.md) -- Core principles, workflow steps, feature flags, and anti-patterns102- [stacked-changes.md](references/stacked-changes.md) -- Stacked PRs concept, manual stacking, Graphite automation, best practices103- [conventional-commits.md](references/conventional-commits.md) -- Commit format, types, scopes, breaking changes, and full workflow104- [github-actions.md](references/github-actions.md) -- Reusable workflows, matrix testing, deployment environments, security105- [git-internals.md](references/git-internals.md) -- Object model, SHA hashing, index, references, packfiles, garbage collection106- [automation-scripts.md](references/automation-scripts.md) -- Branch pruning, semantic release, security scanning, stacked PR helpers107- [issue-templates.md](references/issue-templates.md) -- Bug report, feature request, task, and minimal issue templates108109---110> Converted and distributed by [TomeVault](https://tomevault.io/claim/jbabin91) — claim your Tome and manage your conversions.111<!-- tomevault:4.0:skill_md:2026-04-13 -->
tomevault-io