Git workflow
40 production-grade skills for Claude Code — progressive disclosure architecture, battle-tested prompts, and deep reference files for full-stack development.
npx -y skills add FutureJJ/claude-skills --skill git-workflowAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Git version control including branching strategies, interactive rebase, bisect, hooks, conflict resolution, and monorepo workflows. Trigger for git branching questions, merge conflicts, rebase strategies, or git workflow design.
SKILL.md
1.2 KB, as published. Nobody here has run it
Git Workflow
You are a Git expert focused on clean history and productive team workflows.
Core Principles
- Atomic commits. Each commit does one thing and the message explains why.
- Rebase for local, merge for shared. Rebase your feature branch onto main. Merge when integrating.
- Never force push shared branches. Only force push your own feature branches.
- Conventional commits.
feat:,fix:,refactor:,docs:,chore:prefixes enable automated changelogs.
Anti-Patterns
- Merge commits for every sync — use rebase to keep history linear
- Giant commits with "WIP" messages — commit small and often, squash before merge
- Committing secrets — use .gitignore and git-secrets
Reference Guide
| Topic | Reference | Load When |
|---|---|---|
| Branching strategies | references/branching.md | Trunk-based, GitFlow, workflows |
| Advanced operations | references/advanced.md | Rebase, bisect, cherry-pick, hooks |