How do I install the Git Workflow skill?

Run npx skillmds@latest add tomevault-io/git-workflow-49 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. 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 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?

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

Git Workflow by tomevault-io — Agent Skill

Name: Git Workflow
Author: tomevault-io

Git Workflow

Guide Git workflows including branching strategies, commit conventions, and PR management. Use this skill when users need help with Git operations, branch management, commit messages, or establishing team Git workflows. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Git Workflow Skill

You are an expert in Git version control and team collaboration workflows.

Commit Message Convention

Format

<type>(<scope>): <subject>

<body>

<footer>

Types

Type	Description
feat	New feature
fix	Bug fix
docs	Documentation only
style	Code style (formatting, semicolons)
refactor	Code change that neither fixes nor adds
perf	Performance improvement
test	Adding or updating tests
chore	Build process or auxiliary tools
ci	CI configuration changes

Examples

feat(auth): add OAuth2 login support

Implement Google and GitHub OAuth2 providers.
Users can now link multiple social accounts.

Closes #123

fix(api): handle null response from payment service

The payment service returns null for cancelled transactions.
Added null check to prevent TypeError.

Fixes #456

Branching Strategies

GitHub Flow (Recommended for most teams)

main (production-ready)
  └── feature/add-login
  └── feature/update-dashboard
  └── fix/payment-bug

Rules:

main is always deployable
Create feature branches from main
Open PR when ready for review
Merge to main after approval
Deploy immediately after merge

Git Flow (For scheduled releases)

main (production)
develop (integration)
  └── feature/add-login
  └── release/v1.2.0
  └── hotfix/critical-bug

Rules:

main reflects production
develop is integration branch
Feature branches from develop
Release branches for final prep
Hotfix branches from main

Branch Naming Convention

<type>/<ticket>-<description>

Examples:
feature/AUTH-123-oauth-login
fix/BUG-456-null-pointer
chore/INFRA-789-update-deps

Pull Request Guidelines

PR Title

Follow commit message format:

feat(auth): add OAuth2 login support

PR Description Template

## Summary
Brief description of changes

## Changes
- Change 1
- Change 2

## Testing
- [ ] Unit tests pass
- [ ] Integration tests pass
- [ ] Manual testing completed

## Screenshots (if applicable)

## Related Issues
Closes #123

Review Checklist

Code follows project conventions
Tests are included and passing
Documentation is updated
No sensitive data exposed
Breaking changes are documented

Common Operations

Rebase vs Merge

Use Rebase:

Updating feature branch with main
Cleaning up local commits before PR
Linear history preferred

Use Merge:

Merging PR to main
Preserving branch history
Team policy requires merge commits

Interactive Rebase

# Squash last 3 commits
git rebase -i HEAD~3

# Rebase onto main
git rebase -i main

Undo Operations

# Undo last commit (keep changes)
git reset --soft HEAD~1

# Undo last commit (discard changes)
git reset --hard HEAD~1

# Revert a pushed commit
git revert <commit-hash>

Best Practices

Commit Often, Push Regularly
- Small, atomic commits
- Push at least daily
Write Meaningful Messages
- Explain why, not just what
- Reference issues/tickets
Keep Branches Short-lived
- Merge within days, not weeks
- Delete branches after merge
Review Before Merging
- At least one approval required
- CI checks must pass

Source: roboco-io/plugins — distributed by TomeVault.

---name: git-workflow-49description: Guide Git workflows including branching strategies, commit conventions, and PR management. Use this skill when users need help with Git operations, branch management, commit messages, or establishing team Git workflows. Use when this capability is needed.---# Git Workflow SkillYou are an expert in Git version control and team collaboration workflows.## Commit Message Convention### Format```<type>(<scope>): <subject><body><footer>```### Types| Type | Description ||------|-------------|| feat | New feature || fix | Bug fix || docs | Documentation only || style | Code style (formatting, semicolons) || refactor | Code change that neither fixes nor adds || perf | Performance improvement || test | Adding or updating tests || chore | Build process or auxiliary tools || ci | CI configuration changes |### Examples```feat(auth): add OAuth2 login supportImplement Google and GitHub OAuth2 providers.Users can now link multiple social accounts.Closes #123``````fix(api): handle null response from payment serviceThe payment service returns null for cancelled transactions.Added null check to prevent TypeError.Fixes #456```## Branching Strategies### GitHub Flow (Recommended for most teams)```main (production-ready) └── feature/add-login └── feature/update-dashboard └── fix/payment-bug```**Rules:**- `main` is always deployable- Create feature branches from `main`- Open PR when ready for review- Merge to `main` after approval- Deploy immediately after merge### Git Flow (For scheduled releases)```main (production)develop (integration) └── feature/add-login └── release/v1.2.0 └── hotfix/critical-bug```**Rules:**- `main` reflects production- `develop` is integration branch- Feature branches from `develop`- Release branches for final prep- Hotfix branches from `main`## Branch Naming Convention```<type>/<ticket>-<description>Examples:feature/AUTH-123-oauth-loginfix/BUG-456-null-pointerchore/INFRA-789-update-deps```## Pull Request Guidelines### PR TitleFollow commit message format:```feat(auth): add OAuth2 login support```### PR Description Template```markdown## SummaryBrief description of changes## Changes- Change 1- Change 2## Testing- [ ] Unit tests pass- [ ] Integration tests pass- [ ] Manual testing completed## Screenshots (if applicable)## Related IssuesCloses #123```### Review Checklist- [ ] Code follows project conventions- [ ] Tests are included and passing- [ ] Documentation is updated- [ ] No sensitive data exposed- [ ] Breaking changes are documented## Common Operations### Rebase vs Merge**Use Rebase:**- Updating feature branch with main- Cleaning up local commits before PR- Linear history preferred**Use Merge:**- Merging PR to main- Preserving branch history- Team policy requires merge commits### Interactive Rebase```bash# Squash last 3 commitsgit rebase -i HEAD~3# Rebase onto maingit rebase -i main```### Undo Operations```bash# Undo last commit (keep changes)git reset --soft HEAD~1# Undo last commit (discard changes)git reset --hard HEAD~1# Revert a pushed commitgit revert <commit-hash>```## Best Practices1. **Commit Often, Push Regularly** - Small, atomic commits - Push at least daily2. **Write Meaningful Messages** - Explain why, not just what - Reference issues/tickets3. **Keep Branches Short-lived** - Merge within days, not weeks - Delete branches after merge4. **Review Before Merging** - At least one approval required - CI checks must pass---> Source: [roboco-io/plugins](https://github.com/roboco-io/plugins) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions