Push Changes

Push local changes to the remote repository with safety checks.

Workflow

1. Check current branch

   bashCopy

   git branch --show-current
   

   STOP if on main or master: Warn the user they forgot to create a branch. ALWAYS use the AskQuestion tool:

   • Title: "Branch Required"
   • Question: "You're currently on the main branch. What branch name would you like to use?"
   • Options:
     • id: "custom", label: "Let me specify a branch name"
     • id: "abort", label: "Abort, I'll create it myself"

   If the user selects "custom", ask them conversationally for the branch name, then create and switch to it:

   bashCopy

   git checkout -b <branch-name>
   

2. Check status

   bashCopy

   git status
   

   Review untracked files and modifications.

3. Stage changes

   bashCopy

   git add -A
   

   Or selectively add specific files if the user prefers.

4. Review staged changes

   bashCopy

   git diff --staged --stat
   

5. Commit with descriptive message Analyze the changes and create a commit message following conventional commits format:

   bashCopy

   git commit -m "$(cat <<'EOF'
   <type>(<scope>): <description>
   
   <optional body>
   EOF
   )"
   

   Types: feat, fix, docs, style, refactor, test, chore

6. Push to remote

   bashCopy

   git push -u origin HEAD
   

7. Verify push succeeded

   bashCopy

   git status
   

   Confirm the branch is up to date with remote.

Safety Rules

• Never push to main or master - always create a feature branch first
• Never force push unless explicitly requested by the user
• Review changes before committing to avoid committing secrets or unwanted files