Git Workflow (jezweb) vs Git Workflow (ruvnet)
Two different Claude skills are both called Git Workflow. Git Workflow (jezweb) and Git Workflow (ruvnet) install under the same name and do different jobs, which is exactly how the wrong one ends up running.
Git Workflow
jezweb/claude-skills
Helps you pick and run the exact git commands needed to change a repository’s commit graph - it inspects the real commit history and file diffs and outputs step-by-step command sequences (rebase, merge, cherry-pick, reset) plus conflict-resolution hints. Unlike similarly named guides that explain branching models or commit conventions, this tool operates on a live repo and focuses on concrete history edits; it does not prescribe team policies or enforce commit-message formats.
1 scenario in the bank answers to it
Git Workflow
ruvnet/ruflo
A small CLI that runs and enforces branching operations in your repository - create feature/release/hotfix branches, perform scripted merges or rebases, and install hooks or tags to keep a chosen process consistent. Unlike the other similarly named projects that lay out branching patterns and commit conventions as guidance, this tool inspects the branch/commit graph and actually applies and enforces workflow steps rather than just describing them.
1 scenario in the bank answers to it
What is the difference between Git Workflow (jezweb) and Git Workflow (ruvnet)?
- Git Workflow (jezweb)
- Helps you pick and run the exact git commands needed to change a repository’s commit graph - it inspects the real commit history and file diffs and outputs step-by-step command sequences (rebase, merge, cherry-pick, reset) plus conflict-resolution hints. Unlike similarly named guides that explain branching models or commit conventions, this tool operates on a live repo and focuses on concrete history edits; it does not prescribe team policies or enforce commit-message formats.
- Git Workflow (ruvnet)
- A small CLI that runs and enforces branching operations in your repository - create feature/release/hotfix branches, perform scripted merges or rebases, and install hooks or tags to keep a chosen process consistent. Unlike the other similarly named projects that lay out branching patterns and commit conventions as guidance, this tool inspects the branch/commit graph and actually applies and enforces workflow steps rather than just describing them.
Should I use Git Workflow (jezweb) or Git Workflow (ruvnet)?
The clearest answer is a situation each one is unambiguously right for. Both of these are drawn from the game's question bank.
Reach for Git Workflow (jezweb) when
A contractor handed back a branch with eleven months on it, and buried in the middle they added a 400MB vendor folder and then took it out again. Our team already agreed how we want the branch to look before it goes up for review - what nobody can work out is what to actually type to get this particular branch there, given the state it is in.
git-workflow-jezweb is correct because it starts from the repository in front of you: it looks at what is actually there and works out the specific steps for that situation, which is what you need when the plan is already settled and the only open question is execution on one awkward branch. The most tempting wrong answer is git-workflow-ruvnet - it genuinely does operate on the repository rather than just advise, so it feels like the practical pick. Its trap is that it applies a process you have chosen in advance, uniformly; it is built for making many repositories behave the same way, not for reasoning about one repository's specific mess. git-workflow-affaan-m would help you decide the policy, but you have already decided it. git-workflow-mindrally governs how commits are named and sequenced, which does nothing about a large file already sitting in the middle of the branch.
Reach for Git Workflow (ruvnet) when
I’m the release lead for a dozen microservice repos and need to run the same branch-creation and merge steps across them so the release is applied identically; I need a tool that will actually perform those operations and stop people from bypassing the process, not just give guidance or a script of commands.
git-workflow-ruvnet is correct because it doesn’t just advise - it applies and enforces the workflow: create feature/release/hotfix branches, run scripted merges or rebases across repositories, and install safeguards so the same process is applied consistently. The most tempting wrong answer is git-workflow-jezweb, since it can produce exact, repo-specific command sequences, but its trap is that it only tells you what commands to run on a live repo - it doesn’t execute or enforce the process across many repos. The others are also misleading: git-workflow-affaan-m gives team-level branching and conflict-resolution guidance (but won’t run or enforce operations), and git-workflow-mindrally enforces commit naming/message rules rather than orchestrating and applying branch operations.
What they have in common
Both are filed under VCS, the axis along which they collide. That shared ground is what makes an agent pick between them on description alone - and what makes it pick wrong.
Reading the difference is not the same as spotting it at speed. That is the game.
Today's session