never-auto-push

Require explicit user authorization before executing git push operations.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/NIMBUS-MX/nimbus-skills --skill never-auto-push
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: never-auto-push
Source: https://github.com/NIMBUS-MX/nimbus-skills/tree/main/skills/never-auto-push
Command: npx skills add https://github.com/NIMBUS-MX/nimbus-skills --skill never-auto-push

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that no unauthorized 'git push' operations are performed, mitigating the risk of unintended deployments and code exposure.

Core Features & Use Cases

  • Explicit Authorization: Requires explicit user authorization before any 'git push' operation, reducing the risk of accidental pushes.
  • Pre-commit Hook and Command Trigger: Can be triggered via pre-commit hooks and specific commands, ensuring consistency in deployment practices.
  • Scope and Context: Helps maintain the integrity of the codebase by preventing unauthorized pushes, especially to critical branches like 'main' or 'master'.

Quick Start

Run the 'git push' command after the user has explicitly authorized the push by saying "push".

Frequently Asked Questions about never-auto-push

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent accidental git push to the main branch?

To prevent accidental git push to the main branch, this Skill enforces explicit user authorization before executing any push operation, serving as a safety net against unintended deployments and code exposure.

How do I enforce explicit authorization for git push operations?

You enforce explicit authorization for git push operations by monitoring user input during the commit process, requiring the user to explicitly say "push" to validate and authorize the deployment.

Can I trigger deployment control checks via pre-commit hooks?

Yes, you can trigger deployment control checks via pre-commit hooks and specific commands, ensuring consistency in deployment practices and maintaining the integrity of your codebase in collaborative environments.

What is the best way to protect critical branches from unauthorized deployments?

The best way to protect critical branches from unauthorized deployments is enforcing explicit push authorization, which mitigates risks by validating user permission before any git push operation is performed.

Does this code safety Skill require any dependencies to run?

No, this code safety Skill requires no dependencies to run, providing a lightweight safety net that monitors user input during the commit and push process to validate authorization.