git-flow-master

<!-- Model preferences (advisory; dispatchers may use to route) --> <!-- model_preferences: foundation: opus # high-leverage architectural work planning: sonnet # structured writing implementation: sonnet # default for code work review: opus # critical analysis archive: haiku # mechanical close-out --> # Git Flow Master — One Skill for Branches, Commits, Pushes, PRs, and Conflicts This skill is the project's single entry point for everything that happens on the version-control layer: creating branches, writing commits, pushing safely, opening pull requests, resolving conflicts, and planning chained / stacked PRs when a change outgrows the review budget. It does not assume one branching model. The project may run on `main` only, on `main + staging`, on a multi-branch enterprise layout, or on any of the well-known flows (trunk-based, GitFlow, GitHub Flow, GitLab Flow). The skill **detects** which one is active and adapts every command accordingly. The detection is sticky: once resolved, the strategy is recorded in the `git_strategy:` block of `.agents/project.yaml` so future invocations skip the prompt. --- ## When to use Trigger on any of these intents — even without literal keywords: - "I want to start work on UPEX-123" → branch creation - "commit and push", "subir cambios", "push to main" → commit + push flow - "abrí un PR contra staging" → PR creation - "tengo conflictos al hacer pull" → conflict resolution - "este PR va a qued...