prepush-guard

Enforce formatting, linting, type-checking, and tests before git push.

2|1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/genfeedai/genfeed.ai --skill prepush-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prepush-guard
Source: https://github.com/genfeedai/genfeed.ai/tree/main/.agents/skills/prepush-guard
Command: npx skills add https://github.com/genfeedai/genfeed.ai --skill prepush-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prepush-guard enforces a pre-push quality gate to catch issues before code is pushed. This ensures local verification and reduces CI surprises for monorepo changes.

Core Features & Use Cases

  • Provides a structured checklist to run formatting, linting, type-checking, and tests locally before pushing.
  • Helps ensure changes across apps/packages maintain code quality and consistency in a complex monorepo.
  • Use case: a developer makes edits across multiple services and wants to guarantee all checks pass before opening a PR.

Quick Start

Run the prepush-guard before pushing changes to ensure all checks pass.

Frequently Asked Questions about prepush-guard

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

FAQPage Schema
How do I run lint, format, and tests before pushing changes in a monorepo?

To enforce a pre-push quality gate for monorepo changes, execute formatting, linting, type-checking, and tests locally. This structured checklist runs before git push and PR updates to catch issues early.

What is a pre-push quality gate and when do I need it for monorepo changes?

A pre-push quality gate enforces local formatting, linting, type-checking, and tests before git push. You need it for monorepo changes to catch issues locally and reduce CI surprises when updating multiple apps or packages.

Can I use a pre-push quality gate after substantial edits across multiple packages?

Yes, you can apply a pre-push quality gate after substantial edits across multiple packages. It enforces formatting, linting, type-checking, and tests to ensure changes maintain code quality and consistency before opening a PR.

Why does pushing monorepo changes without local checks cause CI failures?

Pushing monorepo changes without local checks causes CI failures because formatting, linting, type-checking, and tests are not verified locally. A pre-push quality gate catches these issues before code is pushed to reduce CI surprises.

Do I need external dependencies to enforce pre-push checks in a monorepo?

No external dependencies are needed to enforce pre-push checks in a monorepo. The quality gate provides a standalone execution checklist for formatting, linting, type-checking, and tests that runs locally before git push and PR updates.