git-workflow
Skill34 starsChanged 11 months agoMITView on GitHub
Git workflow management. Triggers when creating branches, preparing PRs, or managing merge decisions.
- Deletes or force-pushes
- Commits and pushes
187 other projects use a version of this.
Adopted by
Most recently taken up by
- avpit/claude-skillstheir own version, first seen Nov 16, 2026
- AlejandroGodius/claude-skillstheir own version, first seen Nov 16, 2026
- RichardMcQuiston01/unofficial-claude-skill-examplestheir own version, first seen Nov 16, 2026
- AndresArreguy/ecc-pi-porttheir own version, first seen Nov 16, 2026
- fabioc-aloha/Alex_ACT_ONEtheir own version, first seen Nov 15, 2026
- juninmd/skillstheir own version, first seen Nov 15, 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
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
AGMO-IncSkillplugin-review
Use to analyze plugin usage patterns and suggest improvements. Triggers on "플러그인 리뷰", "plugin review", "사용 패턴 분석".
Also in 3 projects that use this
Galaxy-DawnSkillresults-report
This skill should be used when the user asks to "write an experiment report", "summarize experimental results", "do experiment retrospection", "write a results report", "写实验总结报告", "写实验复盘", or mentions turning completed experiment artifacts into a structured, decision-oriented research report. It assumes strict analysis should come from `results-analysis` first.
Also in 3 projects that use this
- +6 more from Azure
Other versions187 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
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 repository9 other files it gives its agents.
- openspec/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- code-reviewSkill
- continuous-improvementSkill
- dev-workflowSkill
- openapi-workflowSkill
- ralph-invokeSkill
- security-scanSkill
- systematic-debuggingSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 164 edited versions we read keep these.
1
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
- could be automatic: a setting could enforce it
- Distinctive: line 124
Always: run tests before creating PR
“Common” is measured: kept by at least 6 in 10 of the 164 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 Skill
Manage git branches, commits, and pull requests following project conventions.
When to Activate
This skill should activate when:
- Starting work on a new feature/fix
- Creating a new feature branch
- Preparing to create a pull request
- Deciding whether to merge or rebase
- Resolving merge conflicts
Branch Naming Convention
<type>/<short-description>
Examples:
- feature/add-user-profile
- fix/login-redirect-bug
- chore/update-dependenciesCommit Message Format
type: description
Types:
- feat: New feature
- fix: Bug fix
- docs: Documentation
- style: Formatting (no code change)
- refactor: Code restructuring
- test: Adding tests
- chore: Maintenance
Examples:
- feat: add user profile endpoint
- fix: resolve login redirect issue
- chore: update dependenciesWorkflow Steps
1. Start New Work
# Ensure main is up to date
git checkout main
git pull origin main
# Create feature branch
git checkout -b feature/description2. During Development
# Stage changes
git add -p # Interactive staging (review each change)
# Commit with conventional format
git commit -m "type: description"
# Push regularly
git push -u origin branch-name3. Before PR
# Ensure all tests pass
make test # or appropriate test command
# Rebase on latest main (if needed)
git fetch origin main
git rebase origin/main
# Force push after rebase
git push --force-with-lease4. Create PR
# Using GitHub CLI
gh pr create --title "type: description" \
--body "## Summary
- What this PR does
## Test Plan
- How to test"Merge vs Rebase Decision
| Situation | Action |
| Feature branch behind main | Rebase onto main |
| Shared branch (multiple devs) | Merge, don't rebase |
| Before PR | Rebase + squash if messy |
| After PR approved | Squash merge via GitHub |
Conflict Resolution
# During rebase conflict
git status # See conflicted files
# Edit files to resolve conflicts
git add <resolved-files>
git rebase --continue
# If too messy, abort and merge instead
git rebase --abort
git merge origin/mainRules
- Never force push to main/master
- Always run tests before creating PR
- Squash merge feature branches to keep history clean
Output Format
## Git Workflow
**Branch**: `feature/description`
**Base**: `main`
**Commits**: X commits
### Pre-PR Checklist
- [ ] Tests passing
- [ ] Rebased on latest main
- [ ] Commit messages follow convention
- [ ] No merge conflicts
### Ready for PR
```bash
gh pr create --title "..." --body "..."Does 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.

