Safe Git Push FAQs

Question 1

Can I bypass the safety lock if I really need to?

Accepted Answer

No, the safety lock is non-negotiable to prevent human error. If you must push to a protected branch, you should use standard terminal commands outside of this skill.

Question 2

Does it handle upstream tracking for new branches?

Accepted Answer

Yes, if a branch has no upstream set, the skill will use the git push -u origin command to establish tracking automatically.

Question 3

What happens if I try to push from the master branch?

Accepted Answer

Claude will refuse the command, display a clear error message, and provide specific instructions on how to create a feature branch and move your commits there safely.

Question 4

How does this skill protect the main branch?

Accepted Answer

The skill automatically verifies the current branch name and upstream destination before execution; it is hardcoded to block any push commands targeting origin/main or origin/master.

Question 5

Does it support force pushing to feature branches?

Accepted Answer

Yes, it supports standard git options including --force and --force-with-lease for all branches that are not main or master.

Safe Git Push

Key Features

Use Cases

Safe Git Push

Key Features

Use Cases