safe-push

Audit code pushes for secrets and PII before pushing to remotes.

97|18|Updated Feb 9, 2026

Search Tags:#automation #git #audit #push #secrets #pii

Ready to run

npx skills add https://github.com/thatrebeccarae/claude-marketing --skill safe-push-thatrebeccarae

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: safe-push
Source: https://github.com/thatrebeccarae/claude-marketing/tree/main/skills/safe-push
Command: npx skills add https://github.com/thatrebeccarae/claude-marketing --skill safe-push-thatrebeccarae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps prevent accidental leakage of secrets and personal data by auditing code pushes for sensitive content and enforcing safe multi-step push patterns.

Core Features & Use Cases

Pinpoint detection of secrets, tokens, and PII in diffs prior to pushing to public remotes.
Enforces rate-limited and staggered push strategies to avoid triggering automation or abuse detection.
Suggests safe-branch push workflows and rebase-friendly messaging to maintain compliance during release cycles.
Use Case: A team wants to push multiple feature branches to a public repository without exposing credentials in commit history.

Quick Start

Use Safe Push before any git push to ensure PII, secrets, and commit messages meet standards.

Frequently Asked Questions about safe-push

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

FAQPage Schema

How do I audit code pushes for secrets and PII before pushing to a remote?▼

To audit code pushes for secrets and PII, scan your diffs and commit messages prior to execution. This process detects sensitive content and enforces blocklist rules across single and multi-branch pushes before any data reaches a remote repository.

What is the best way to prevent accidental leakage of secrets during multi-branch pushes?▼

The best way to prevent accidental leakage of secrets during multi-branch pushes is to enforce staggered execution and rate limits. This safe multi-step push pattern diff-scans branches and controls push rates to avoid exposing credentials in commit history.

Does this pre-push audit work with both public and private repositories?▼

Yes, this pre-push audit works with both public and private repositories. It applies diff scanning, commit-message checks, blocklist enforcement, and push-rate control across all remote targets to ensure sensitive data compliance.

How do I check commit messages for sensitive data before a git push?▼

To check commit messages for sensitive data before a git push, apply pre-push commit-message checks. This scans message content against a blocklist and compliance standards to ensure no secrets or PII are transmitted to the remote.

Can I enforce rate limits and staggered push strategies across multiple feature branches?▼

Yes, you can enforce rate limits and staggered push strategies across multiple feature branches. This controls multi-branch push execution rates to avoid triggering automation or abuse detection on the remote repository.