thatrebeccarae/claude-marketing / skills/safe-push
safe-push
VerifiedPre-push hygiene check for GitHub repositories. Scans for PII, secrets, and sensitive data before pushing. Audits commit messages, enforces repo-specific blocklists, and rate-limits pushes to avoid GitHub abuse detection. Use before any git push, especially to public repos.
| File | Kind | Size |
|---|---|---|
| EXAMPLES.md | markdown | 1.8 KB |
| LICENSE | other | 1.0 KB |
| REFERENCE.md | markdown | 4.2 KB |
| SKILL.md | skill md | 7.6 KB |
| safe-push-blocklist.template | other | 1.4 KB |
EXAMPLES.md
View on GitHub# Safe Push — Examples
## Example 1: Standard Push to Public Repo
**Prompt:**
> Push my changes to the public repo.
**Expected behavior:**
1. Detects `.public-repo` marker → applies all checks
2. Scans diff: finds no secrets or PII
3. Audits commit messages: all descriptive, no blocked terms
4. Summary: "Public repo, 3 commits on main, no issues found. Push directly?"
5. User confirms → pushes → verifies with `git log`
---
## Example 2: PII Detected in Diff
**Prompt:**
> Push this branch to origin.
**Expected behavior:**
1. Scans diff → finds issues:
- `config.py:12` — email address `john.doe@company.com`
- `settings.json:8` — private IP `192.168.1.50`
- `.env.example:3` — looks like a real API key `sk-live-abc123...`
2. Reports all findings with file and line number
3. Blocks push: "3 issues found. Fix these before pushing."
4. Does NOT push until resolved
---
## Example 3: Vague Commit Messages
**Prompt:**
> Safe push to the public repo.
**Expected behavior:**
1. PII scan passes
2. Commit message audit flags:
- `a1b2c3d fix` — too vague, suggest: "fix: [describe what was fixed]"
- `e4f5g6h update` — too vague, suggest: "update: [describe what changed]"
3. Suggests interactive rebase to clean messages (with user approval)
4. Does not push until messages are acceptable
---
## Example 4: Large Push with Staggering
**Prompt:**
> Push all branches to the new public remote.
**Expected behavior:**
1. Detects multiple branches: main (120 commits), develop (45 commits), feature/auth (8 commits)
2. PII scan on all branches — clean
3. Proposes staggered strategy:
- Push `main` first (in batches of 50: 3 batches, 10s gaps)
- Wait 10s
- Push `develop` (single push, < 50 commits)
- Wait 5s
- Push `feature/auth` (single push)
4. User confirms → executes with progress updates
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |