What problem does it solve? Pushing code to a shared repository carries risks: accidentally pushing directly to protected branches like main or master, force-pushing over teammates' commits, or pushing with uncommitted changes. This Skill enforces a safe, checklist-driven push workflow aligned with Git Flow conventions. ## Core Features & Use Cases - Branch Rule Enforcement: Dynamically detects the main branch (main or master) and blocks direct pushes to it, redirecting users to pull requests instead. - Pre-Push Checklist: Shows current branch, commits to be pushed, remote configuration, and uncommitted changes before executing any push. - Safe Force Push Handling: Recommends --force-with-lease over --force and refuses force pushes to protected branches entirely. - Use Case: A developer finishes work on a feature branch and says "푸시해줘" (push it). The Skill verifies the branch is feature/*, lists the 3 commits to be pushed, confirms no uncommitted changes exist, and runs git push -u origin with upstream tracking. ## Quick Start Ask the assistant to push your current branch to the remote by saying "push my commits" or "/git-push".