GitFlow

**Quick judgment** GitFlow is a focused skill for teams working across GitHub and GitLab that want a more automated, unified way to push code and see CI/CD results. It’s most valuable if your developers are already comfortable with git and CLI tools (gh, glab) and you want to standardize a “push + watch pipeline” workflow. **Strengths** - Consolidates the common workflow of: push → check pipeline → inspect logs across GitHub and GitLab. - Uses well-known CLIs (gh, glab) rather than opaque custom integrations, which aids debugging and predictability. - Example commands and the provided `git pushflow` alias make it straightforward to adopt in an existing CLI-centric workflow. **Risks & limitations** - Requires correct setup of gh/glab authentication and permissions; misconfiguration can cause confusing failures or partial visibility of pipelines. - Auto-pushing from a skill/alias can increase the risk of pushing unreviewed or WIP changes if developers are not careful. - Functionality appears focused on triggering pushes and monitoring CI, not on richer release orchestration (e.g., multi-env promotion, approvals, rollbacks). - Tied to GitHub and GitLab; other hosting platforms (Bitbucket, Azure DevOps, self-hosted alternatives without gh/glab equivalents) are out of scope. **Recommended scenarios** - Teams with mixed GitHub + GitLab repos who want a single, repeatable way to push and immediately observe CI status. - Individual developers who prefer working in the terminal and want to avoid opening multiple web dashboards after every push. - Projects where quick feedback on pipeline breakage is important, but complex deployment orchestration is handled elsewhere. **Less ideal scenarios** - GUI-first teams who rarely use gh/glab or terminal-based workflows. - Organizations needing advanced release management, multi-stage promotion, or policy enforcement beyond basic CI monitoring. - Environments where strict controls on who/what can push to remotes make automated push helpers undesirable.