pre-push

Scan staged git changes for secrets and block pushes on critical issues.

123|22|Updated Apr 7, 2026

Search Tags:#git #security #agents #pipeline #secrets #lint #pre-push

Ready to run

npx skills add https://github.com/AlexZio00/claude-code-skills --skill pre-push-alexzio00

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pre-push
Source: https://github.com/AlexZio00/claude-code-skills/tree/main/pre-push
Command: npx skills add https://github.com/AlexZio00/claude-code-skills --skill pre-push-alexzio00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Pre-Push Pipeline provides a mandatory gate that runs security, quality, and policy checks before any git push, preventing leakage of credentials and ensuring code quality.

Core Features & Use Cases

Enforces a mandatory secret scan on staged changes to block hardcoded credentials and tokens.
Performs structured reviews of code quality and governance gates, surfacing critical issues before they reach remote branches.
Applies a multi-step review flow with automated remediation suggestions when issues are found, and safeguards to handle override scenarios.

Quick Start

Execute the pre-push gate on staged changes to verify secrets, security, and quality before every push.

Frequently Asked Questions about pre-push

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

FAQPage Schema

How do I prevent secrets and credentials from leaking when pushing code to git?▼

You can automate a pre-push gate that enforces secret scanning on all staged changes. This prevents hardcoded credentials and tokens from reaching remote branches by blocking the push when critical security issues are detected.

What checks should I run before a git push to ensure code quality and security?▼

A pre-push gate should run secrets scanning, supply-chain checks, and lint gates on staged changes. This multi-step review flow surfaces critical governance risks and code quality issues before they reach protected branches.

How do I set up a pre-push pipeline for protected branches?▼

You execute a pre-push gate on staged changes to verify secrets, security, and quality before every push. This applies mandatory checks to all staging changes, ensuring only verified code reaches your protected branches.

Can I override pre-push checks during an emergency deployment?▼

Yes, the pre-push pipeline includes safeguards to handle override scenarios for emergencies. This allows you to bypass the security and quality gate when critical situations require immediate code deployment to protected branches.

Does the pre-push gate provide automated remediation for lint and security issues?▼

The pre-push pipeline applies a multi-step review flow with automated remediation suggestions when issues are found. This helps resolve detected security and quality problems before the push proceeds to remote branches.