push-safe

What problem does it solve?

This skill prevents accidental pushes and credential exposure by pushing a Srtforge branch only when the user explicitly asks, keeping sensitive data out of Git operations.

Core Features & Use Cases

• Guarded pushes: Validates intent before pushing and prevents main or protected branches from being pushed without explicit authorization.
• Credential safeguards: Ensures no credentials or tokens are exposed through remote URLs or Git config during the push process.
• Status checks: Verifies current branch, remotes, and diff/staging status prior to execution.
• Use Case: A developer requests a push of a feature branch to origin after code review, with confidence that credentials are not leaked and main remains untouched.

Quick Start

Ask the AI to push the current local branch to origin only after you explicitly authorize it.