Branch Workflow & Merge Queue Skill

Preventing direct commits to your main branch requires a strict Git workflow with multiple layers of protection. This Skill enforces this by guiding development through isolated worktrees and automated pull request creation before any code merges.

Automating a Git merge queue involves managing an event-driven process that handles rebasing and merging once CI checks pass. This Skill manages the queue automatically, ensuring merges only happen when Continuous Integration pipelines are green.

Using Git worktrees creates isolated development environments for each task, ensuring you always start with the latest code from main. This Skill automatically sets up these worktrees to keep feature development separated and clean.

When CI failures or merge conflicts occur during an automated pull request merge, the process halts to prevent broken code integration. This Skill handles these failures directly and provides emergency procedures for resolving critical situations.

Yes, you can integrate an automated merge queue into your existing CI/CD development process. The Skill manages event-driven merge queues that handle rebasing and merging automatically once your Continuous Integration checks pass.

No specific Git extensions or dependencies are required to manage worktrees and pull requests with this Skill. It operates independently using standard Git branching, committing, and CI pipeline configurations to enforce the development process.