git-push

Automate pre-push verification of README, tests, linting, and secrets.

Updated Dec 15, 2025

Search Tags:#code-quality #ci-cd #pre-push #secret-scanning #git-push #commit-hygiene #branch-verification

Ready to run

npx skills add https://github.com/scruffydan/AI-Agents --skill git-push-scruffydan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-push
Source: https://github.com/scruffydan/AI-Agents/tree/main/source/skills/git-push
Command: npx skills add https://github.com/scruffydan/AI-Agents --skill git-push-scruffydan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides pre-push checks to ensure code pushes are safe, compliant, and well-documented.

Core Features & Use Cases

Pre-push verification: README, tests, lint, and formatting checks before pushing.
Security checks: secret scanning and credential exposure prevention during the push workflow.
Branch/remote status: verify alignment with the main branch and remote status before pushing.

Quick Start

Use this skill before pushing to verify changes are ready for review and release.

Frequently Asked Questions about git-push

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

FAQPage Schema

How do I automate pre-push checks for secret scanning and linting in Git?▼

Pre-push verification automates checks for README presence, test results, linting, and secret scanning before code reaches shared branches. It enforces commit hygiene and prevents credential exposure during the push workflow.

What is the best way to enforce commit hygiene and branch verification before pushing code?▼

A pre-push verification workflow enforces commit hygiene by checking commit messages, verifying branch status, and ensuring remote alignment. This prevents untested or non-compliant code from reaching shared branches.

Can I verify README updates and test results as part of my CI-CD pre-push workflow?▼

Yes, pre-push verification workflows can check for README presence and validate test results. This ensures documentation is updated and code passes tests before being pushed to shared branches.

Does pre-push secret scanning prevent credentials from being pushed to shared branches?▼

Yes, pre-push secret scanning prevents credentials from being pushed to shared branches. It detects exposed secrets in the changes and halts the push if sensitive data is found.

How do I check branch status and remote alignment before a Git push?▼

You can check branch status and remote alignment by running a pre-push verification workflow. This validates your local branch against the remote main branch to ensure changes are ready for review and release.