pre-push

Run tests, format, lint, and branch-name checks before pushing.

4|Updated Dec 31, 2025
One-click install
npx skills add https://github.com/Taketo-Yoda/uv-sbom --skill pre-push
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-push
Source: https://github.com/Taketo-Yoda/uv-sbom/tree/main/.claude/skills/pre-push
Command: npx skills add https://github.com/Taketo-Yoda/uv-sbom --skill pre-push

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces local pre-push validations to ensure code quality and CI readiness before pushing to a remote repository.

Core Features & Use Cases

  • Runs the full pre-push validation suite (tests, formatting, linting) to catch issues early.
  • Checks branch naming conventions to enforce workflow standards.
  • Reports results clearly and aborts pushes when failures are detected.
  • Useful for solo developers and teams adhering to strict code quality gates before CI runs.

Quick Start

Run the /pre-push skill before pushing to ensure all checks pass.

Frequently Asked Questions about pre-push

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

FAQPage Schema
How do I run pre-push checks locally before pushing to a remote git repository?

Pre-push checks enforce local validations for tests, formatting, linting, and branch naming to ensure code quality before pushing to a remote git repository. They abort pushes on failures and guide developers to resolve issues.

Can I enforce branch naming conventions before a git push?

Yes, you can enforce branch naming conventions before a git push by running local pre-push checks. The validation suite verifies branch names against workflow standards and aborts the push if naming conventions are violated.

How do I abort a git push when local tests or linting fail?

To abort a git push when tests or linting fail, run a local pre-push validation suite that executes checks and blocks the push upon detecting failures. This prevents broken code from reaching the remote repository and CI pipeline.

Do I need pre-push checks if I already have CI pipelines running tests?

Pre-push checks are useful even with CI pipelines because they catch formatting, linting, and test failures locally before pushing. This reduces failed CI runs and saves development time by providing immediate feedback and resolution guidance.

What's the best way to ensure code quality before pushing to CI?

The best way to ensure code quality before pushing to CI is running a local pre-push validation suite that applies tests, format, lint, and branch-name checks. This enforces strict quality gates locally and prevents broken pushes.