push-safe

Verifies branch, remotes, and staged changes before executing an authorized push.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/StiensGate928/Srtforge --skill push-safe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: push-safe
Source: https://github.com/StiensGate928/Srtforge/tree/main/.agents/skills/push-safe
Command: npx skills add https://github.com/StiensGate928/Srtforge --skill push-safe

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about push-safe

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

FAQPage Schema
How do I prevent accidental git pushes to protected branches?

To prevent accidental git pushes, this skill enforces guardrails that verify explicit user authorization before pushing, ensuring main and protected branches remain untouched without confirmation.

Can I push a local git branch without exposing credentials in remote URLs?

Yes, you can push safely because the skill applies credential safeguards that prevent tokens or sensitive data from being exposed through remote URLs or Git config during operations.

What is checked before executing a guarded git push?

Before executing a guarded git push, the skill verifies the current branch, remote targets, and staged changes to validate intent and ensure only authorized modifications are submitted.

How do I automate safe branch pushes that require explicit authorization?

You automate safe branch pushes by asking the AI to push only after explicit authorization, triggering status checks that validate remotes and staging before executing the command.

When should I use strict push control for my Git workflows?

Use strict push control for Git workflows requiring protection of main branches and personal tokens, especially when frontmatter discovery and safety requirements demand guarded operations.

Does the safe push skill work without additional dependencies?

Yes, the safe push skill operates without additional dependencies, using built-in Git workflow validations to enforce guardrails and prevent credential leakage during branch operations.