git-workflow
Skill5 starsChanged 10 months agoMITView on GitHub
Git workflows, conventional commits, branching strategies, and PR management. Use for commits, branches, merges, rebases, and PR workflows.
- Deletes or force-pushes
- Commits and pushes
188 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Rojios/everything-claude-codetheir own version, first seen Nov 8, 2026
- kinhluan/skillstheir own version, first seen Nov 8, 2026
- juninmd/skillstheir own version, first seen Nov 8, 2026
- jDxve/avengers-kittheir own version, first seen Nov 8, 2026
- lhbsaa/apex-unifiedtheir own version, first seen Nov 8, 2026
- haythamasalama/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use squad-commands, ci-cd-pipelines and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Microsoft AzureSkillsquad-commands
Categorized catalog of common Squad operations. Coordinator reads this file and presents it as an interactive menu when the user asks for available commands or help.
Also in 5 projects that use this
harrissohail6Skillci-cd-pipelines
CI/CD pipeline design and implementation. Auto-activates when discussing deployment, automation, or pipelines.
Also in 6 projects that use this
Microsoft AzureSkillarchitectural-proposals
How to write comprehensive architectural proposals that drive alignment before code is written
Also in 4 projects that use this
GitHubSkille2e-template-testing
End-to-end validation of coordinator and agent template changes
Also in 3 projects that use this
GitHubSkillnotification-routing
Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding
Also in 3 projects that use this
frostneySkillnative-nostalgia-stack
Applies the user's FreePascal toolchain and its build, formatting, hook, and test contracts while leaving project-specific mechanics local. Use when scaffolding or working in a FreePascal project that follows this toolchain.
Also in 3 projects that use this
- +5 more from Azure
- +1 more from github
Other versions188 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- wldandan/claude-skills-tutorials★ 111% same
Wrote their own version · 187
- langfuse/langfuse★ 37ksame name
- modelcontextprotocol/typescript-sdk★ 14ksame name
- JetBrains/ideavim★ 10ksame name
- jokob-sk/NetAlertX★ 7.4ksame name
- netalertx/NetAlertX★ 7.4ksame name
- Galaxy-Dawn/claude-scholar★ 5.9ksame name
- github/gh-aw★ 5.6ksame name
- modelcontextprotocol/csharp-sdk★ 4.6ksame name
- antonbabenko/pre-commit-terraform★ 3.8ksame name
- github/squad★ 3.4ksame name
177 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- agent-browserSkill
- apple-docsSkill
- changelog-generatorSkill
- code-reviewSkill
- database-cliSkill
- docker-cliSkill
- github-actionsSkill
- lighthouse-auditSkill
- testingSkill
- vercel-cliSkill
- xcode-mcp-app-testingSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 165 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 199
Small PRs: Keep changes focused, < 400 lines
- Distinctive: line 200
Clear title: Use conventional commit format
“Common” is measured: kept by at least 6 in 10 of the 165 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
git-workflow
Git workflows, conventional commits, branching strategies, and pull request management.
Conventional Commits
Format: <type>(<scope>): <description>
Types
feat: New feature
fix: Bug fix
docs: Documentation only
style: Formatting, no code change
refactor: Code change, no feature/fix
perf: Performance improvement
test: Adding tests
chore: Build, config, dependencies
ci: CI/CD changes
revert: Revert previous commitExamples
git commit -m "feat(auth): add OAuth2 login"
git commit -m "fix(api): handle null response"
git commit -m "docs: update README installation"
git commit -m "chore(deps): upgrade React to 19"
git commit -m "refactor(utils): simplify date formatting"Breaking Changes
git commit -m "feat(api)!: change response format"
# or
git commit -m "feat(api): change response format
BREAKING CHANGE: Response now returns array instead of object"Branch Naming
Format
<type>/<ticket>-<description>Examples
git checkout -b feat/AUTH-123-oauth-login
git checkout -b fix/BUG-456-null-pointer
git checkout -b chore/upgrade-dependencies
git checkout -b hotfix/security-patchTypes
feat/ Feature branch
fix/ Bug fix branch
hotfix/ Urgent production fix
chore/ Maintenance
docs/ Documentation
refactor/ Code refactoring
test/ Test additionsCommon Workflows
Start New Feature
git checkout main
git pull origin main
git checkout -b feat/TICKET-123-feature-nameCommit Changes
git add -A
git commit -m "feat(scope): description"Push and Create PR
git push -u origin HEAD
gh pr create --title "feat(scope): description" --body "## Summary\n- Change 1\n- Change 2"Update Branch with Main
# Rebase (clean history)
git fetch origin
git rebase origin/main
# Or merge (preserves history)
git merge origin/mainInteractive Rebase (squash commits)
git rebase -i HEAD~3 # Last 3 commits
# Change 'pick' to 'squash' or 's' for commits to combineAmend Last Commit
git add .
git commit --amend --no-edit # Keep same message
git commit --amend -m "new message" # Change messageUndo Commits
git reset --soft HEAD~1 # Undo commit, keep changes staged
git reset --mixed HEAD~1 # Undo commit, keep changes unstaged
git reset --hard HEAD~1 # Undo commit, discard changesCherry Pick
git cherry-pick <commit-hash>
git cherry-pick <hash1> <hash2> # Multiple commitsStash Changes
git stash # Stash changes
git stash -m "description" # With message
git stash list # List stashes
git stash pop # Apply and remove
git stash apply # Apply and keep
git stash drop # Remove stashGit Log
git log --oneline -10 # Last 10 commits, compact
git log --oneline --graph --all # Visual branch graph
git log --since="1 week ago" # Last week
git log --author="name" # By author
git log --grep="fix" # Search message
git log -p # Show diffs
git log --stat # Show file changesGit Diff
git diff # Unstaged changes
git diff --staged # Staged changes
git diff HEAD~3 # Last 3 commits
git diff main..feature # Between branches
git diff --name-only # Only file namesTags
git tag v1.0.0 # Lightweight tag
git tag -a v1.0.0 -m "Release 1.0.0" # Annotated tag
git push origin v1.0.0 # Push tag
git push origin --tags # Push all tags
git tag -d v1.0.0 # Delete local tag
git push origin :refs/tags/v1.0.0 # Delete remote tagClean Up
git branch -d feature-branch # Delete merged branch
git branch -D feature-branch # Force delete branch
git remote prune origin # Clean stale remote refs
git gc # Garbage collectAliases (add to ~/.gitconfig)
[alias]
co = checkout
br = branch
ci = commit
st = status
lg = log --oneline --graph --all
last = log -1 HEAD
unstage = reset HEAD --
amend = commit --amend --no-editPR Best Practices
- Small PRs: Keep changes focused, < 400 lines
- Clear title: Use conventional commit format
- Description: Explain what and why
- Tests: Include relevant tests
- Self-review: Review your own diff first
- Screenshots: For UI changes
Merge Strategies
# Merge commit (preserves history)
git merge feature-branch
# Squash merge (single commit)
git merge --squash feature-branch
git commit -m "feat: feature description"
# Rebase merge (linear history)
git rebase main
git checkout main
git merge feature-branch --ff-onlyTroubleshooting
Undo pushed commit
git revert <commit-hash>
git pushFix detached HEAD
git checkout main
# Or save changes:
git checkout -b new-branchRecover deleted branch
git reflog # Find commit hash
git checkout -b recovered-branch <hash>Resolve merge conflicts
git status # See conflicted files
# Edit files, resolve conflicts
git add <resolved-files>
git commit # Complete mergeDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

