ci-stability-hooks

Configure pre-commit and pre-push gates aligned with GitHub Actions.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/jey3dayo/apm-workspace --skill ci-stability-hooks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-stability-hooks
Source: https://github.com/jey3dayo/apm-workspace/tree/main/catalog/skills/ci-stability-hooks
Command: npx skills add https://github.com/jey3dayo/apm-workspace --skill ci-stability-hooks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps maintain code quality by setting up and configuring pre-commit and pre-push gates, aligning with CI workflows to reduce CI failures.

Core Features & Use Cases

  • Pre-commit Configuration: Configure pre-commit hooks for staged files, like formatters and fast linters.
  • Pre-push Configuration: Set up pre-push gates for CI-equivalent checks, like tests, builds, and typechecks.
  • GitHub Actions Alignment: Ensure local gates cover the same checks as CI, without including deploy or production jobs.
  • Verification & Review: Run validations and reviews to confirm the setup is effective and secure.

Quick Start

Use the ci-stability-hooks skill to set up pre-push gates for your project, aligning them with your CI pipeline.

Frequently Asked Questions about ci-stability-hooks

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

FAQPage Schema
How do I align pre-commit and pre-push hooks with GitHub Actions CI?

Align pre-commit and pre-push hooks with GitHub Actions by configuring local gates to run CI-equivalent checks, ensuring tests and builds pass locally before triggering remote CI workflows to reduce failures.

What is the best way to prevent CI failures using local Git hooks?

Prevent CI failures by setting up pre-push gates that execute CI-equivalent checks like typechecks and builds locally, catching integration issues before code reaches the remote repository and triggers a pipeline.

Do I need Lefthook to configure pre-push gates for my repository?

Yes, configuring pre-push gates requires Lefthook along with specific repository configurations to manage staged-file formatters and align local checks with continuous integration workflows effectively.

Can I run staged-file formatters in a pre-commit hook without affecting the CI pipeline?

Yes, pre-commit hooks configure staged-file formatters and fast linters that execute locally on changed files, completely independent of deploy or production jobs in your GitHub Actions CI pipeline.

Why should I separate pre-commit and pre-push gates for code quality checks?

Separating gates places fast formatters in pre-commit for immediate feedback, while heavier CI-equivalent checks like tests and typechecks run in pre-push, optimizing developer workflow and ensuring CI stability.

How do I verify that my local pre-push hooks match my GitHub Actions CI checks?

Verify local pre-push hooks match GitHub Actions by running validations and reviews to confirm the setup covers the same checks as CI, excluding deploy or production jobs, ensuring effective and secure alignment.