git-workflowlisted

# Git Workflow — Release-Branch Model Enforce the release-branch Git model and help execute the correct git operations for your current context: start new work, open a PR, cut a release, or view the workflow reference. ## Hard Rules (always enforced, no exceptions) - **Never commit or push directly to `main`.** If the current branch is `main`, stop and create a new branch before making any changes. - **Never force-push to `main`.** - All changes must reach `main` via a PR from a release branch. ## Instructions When invoked, ask the user what they want to do (if not already specified): > "What would you like to do? > (a) View the Git workflow reference > (b) Start new work — scaffold a feature or fix branch > (c) Open a PR for the current branch > (d) Cut a release — merge release branch to main and tag > (e) Resolve a merge conflict on the current branch > (f) Manage stashes — list, view, apply, or drop stashes" Then execute the appropriate action below. --- ### Action (a) — View Workflow Reference Print the full Git Workflow Reference section below. --- ### Action (b) — Start New Work 1. Use Bash to identify the current release branch: ```bash git branch -r | grep release | sort -V | tail -1 ``` **No-release-branch fallback:** If the command above returns no output (no `release/*` branch exists), fall back to branching from `main` and target `main` for the PR. Inform the user: > "No release branch found. Branching from `main` and the PR will targ