phase-gated-commits
Phase-gated commit workflow for clean git history -- implement, review, test, commit per phase
npx skills add vibeeval/vibecosystem --skill phase-gated-commits --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Phase-Gated Commits Break large features and refactoring into discrete phases. Each phase follows a strict implement -> review -> test -> commit cycle. The result is a clean, bisectable git history where every commit represents a working state. ## When to Use - Multi-file features where changes span 3+ files - Refactoring that touches shared code used by many modules - Any work where you want the ability to revert one phase without losing others - Migrations or upgrades that should be applied incrementally ## When NOT to Use - Single-file changes or small fixes - Exploratory work where the final shape is unknown - Prototyping where speed matters more than history ## Phase Structure Break the work into 2-5 phases. Each phase should: - Be independently functional (the codebase works after each commit) - Have a clear scope (you can describe it in one sentence) - Be reviewable in isolation (a reviewer can understand the diff without needing other phases) ### Phase Sizing | Phase Size | Guideline | |-----------|-----------| | Too small | Renaming a single variable is not a phase | | Right size | Add the data model + migration + basic tests | | Too large | Implement entire feature end-
- When to Use
- When NOT to Use
- Phase Structure
- Phase Sizing
- Workflow Per Phase
- Step 1: Implement
- Step 2: Review
- Step 3: Test
- Step 4: Commit
- Step 5: Pause
- Rules
- Integration with Plan Documentation
What does the phase-gated-commits skill do?
Phase-gated commit workflow for clean git history -- implement, review, test, commit per phase
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill phase-gated-commits --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vibeeval/vibecosystem, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.