Standardize squad git branching from dev with worktree-based parallel execution.
npx skills add https://github.com/elbruno/md-to-slides --skill git-workflow-elbruno
Please help me install this Agent Skill. Skill: git-workflow Source: https://github.com/elbruno/md-to-slides/tree/main/.copilot/skills/git-workflow Command: npx skills add https://github.com/elbruno/md-to-slides --skill git-workflow-elbruno
The git-workflow Skill prevents inconsistent branching, PR targeting, and release practices by standardizing how teams collaborate on dev-first feature delivery with clear promotion channels.
dev rather than main, reducing integration risk.squad/{issue-number}-{kebab-case-slug} convention for traceability.git worktree to run simultaneous issue changes safely within one repo without branch switching conflicts.Ask the assistant to generate a step-by-step plan to create a squad/195-fix-version-stamp-bug branch from dev, open a draft PR targeting dev, and set up safe parallel work using git worktree for two additional issues.
High-intent search queries and answers about installing and using this skill.
A standardized git branching model enforces dev-first feature branching, consistent branch naming, and correct PR base targeting to reduce integration risk. It guides issue-driven work from branch creation through draft PR workflows to deterministic post-merge cleanup.
Git worktree enables safe parallel execution by allowing simultaneous issue changes within one repository without branch switching conflicts. It creates separate working directories for each issue, letting you run multiple branches concurrently and independently.
Coordinated multi-repo dependency changes require dependency-first merge ordering across downstream repositories. You create aligned pull requests in each repository and merge the dependency repository first before promoting downstream changes.
Yes, a promotion pipeline can align git branches with npm publish tags by mapping dev, insiders, and main branches to corresponding npm dist-tags. This ensures deterministic release promotion from development through insiders to production releases.
Consistent branch naming using the squad/{issue-number}-{kebab-case-slug} convention directly links branches to their originating issues. This traceability helps track feature delivery status and automates post-merge cleanup across the promotion pipeline.
You should avoid branching feature work from main when using a dev-first promotion pipeline because it increases integration risk. Feature branches should originate from dev to keep main stable for production releases and ensure proper promotion ordering.
otrebuScan Git repositories under ~/dev and summarize today's commits, branches, and file changes.
quaid-appEnforce a dev-first three-branch model with issue-based workflows and PR merges.
TwuanMinnAutomate GitHub PR reviews, issue triage, and CI/CD workflows.
kimasplundStandardize Git workflows, commit messaging, and branching strategies across teams.