What problem does it solve?
This Skill prevents accidental or premature changes from reaching the canonical main branch by enforcing a consistent Git branching, push, and verification workflow that requires explicit user approval.
Core Features & Use Cases
- Test-branch first workflow: Creates and uses
test/* branches for new features, fixes, and skill work to isolate changes.
- Gated promotion to dev and main: Pushes to
dev only after user confirmation that the work is working, then pushes to main only after dev integration is validated and the user explicitly approves.
- Pre-push quality and safety checklist: Verifies clean diffs against the last known working commit, checks for junk/unintended file changes, and recommends lightweight validation before any push.
- Paired/variant testing guidance: Encourages testing a base feature and a variant to prove extensibility rather than only a single happy-path case.
- Merge conflict and rollback playbooks: Provides command-level guidance for conflict resolution, undoing mistaken pushes, and reverting changes before they propagate.
Quick Start
Use git-workflow to manage a change by creating a test/<task-name> branch, committing your work, asking for confirmation to push to dev, then asking for approval before merging into and pushing to main.