pre-push-gates

Run Prettier and ESLint fixers and deterministic probes on staged changes.

3|2|Updated May 12, 2026
One-click install
npx skills add https://github.com/kriscendobot/garden --skill pre-push-gates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-push-gates
Source: https://github.com/kriscendobot/garden/tree/main/skills/pre-push-gates
Command: npx skills add https://github.com/kriscendobot/garden --skill pre-push-gates

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, yarn, and includes scripts (resource) components.

What problem does it solve?

This Skill prevents common maintainer complaints and code quality regressions by enforcing a strict, automated gate before any code is pushed to a pull request branch.

Core Features & Use Cases

  • Automated Style Enforcement: Silently runs Prettier and ESLint to fix formatting and linting issues, re-staging the changes automatically.
  • Deterministic Probes: Executes a suite of garden-specific checks to catch non-obvious issues like non-ASCII characters, naming stutters, and improper JSDoc imports.
  • Use Case: Before pushing a new feature, the gate ensures your code adheres to project-specific standards, such as avoiding abbreviations in identifiers or ensuring typedefs are correctly located in d.ts files, failing early if manual intervention is required.

Quick Start

Run the pre-push-gates skill to validate the current working directory against all project-specific deterministic rules before your next push.

Frequently Asked Questions about pre-push-gates

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

FAQPage Schema
How do I automate linting and type checking before a git push?

Automated linting and type checking before a git push is enforced by executing automated fixers and custom validation probes on staged changes. This ensures only compliant code reaches the review panel without manual oversight.

How does a deterministic quality gate work in a pull request workflow?

Deterministic quality gates in a pull request workflow operate within a state machine's PR-open and follow-up push workflows. They execute custom validation probes to catch non-obvious issues like non-ASCII characters and improper JSDoc imports.

Can I use Prettier and ESLint to automatically fix and re-stage code?

Yes, Prettier and ESLint can silently run to fix formatting and linting issues, automatically re-staging the changes. This automated style enforcement prevents common maintainer complaints and code quality regressions.

What are the limitations of automated fixers for project-specific code standards?

Automated fixers for project-specific code standards fail early if manual intervention is required for issues like naming stutters or incorrect typedef locations. They cannot automatically resolve all custom heuristic analysis failures without developer input.

Do I need jq and yarn to enforce code quality standards in GitHub PRs?

Yes, jq and yarn are required dependencies to run the scripts that enforce deterministic code quality standards and style consistency. These tools facilitate the automated validation probes executed on staged changes.