verify-before-push

Name: verify-before-push
Availability: InStock
Author: alasdairnc

Run unit, E2E, and security checks before pushing code.

Updated Mar 9, 2026

Search Tags:#ci-cd #guardrails #pre-push #unit-tests #e2e-tests #security-scan

Ready to run

npx skills add https://github.com/alasdairnc/casedive --skill verify-before-push

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-before-push
Source: https://github.com/alasdairnc/casedive/tree/main/.claude/skills/verify-before-push
Command: npx skills add https://github.com/alasdairnc/casedive --skill verify-before-push

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents regressions by automatically validating code changes with a full pre-push verification stack before pushes.

Core Features & Use Cases

Automatically start the local dev server if needed and verify API availability.
Run unit tests, component tests, and end-to-end tests to ensure core functionality.
Include a security scan and guardrails checks to surface vulnerabilities or policy violations before merging.

Quick Start

Run the verify-before-push command to execute the full pre-push verification stack and surface failures for immediate remediation.

Frequently Asked Questions about verify-before-push

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

FAQPage Schema

How do I run pre-push verification to catch regressions before pushing code?▼

Pre-push verification catches regressions by orchestrating unit tests, E2E tests, dev server readiness checks, and security scans sequentially. It reports failures immediately without proceeding to push, ensuring code changes are fully validated.

What is included in a full pre-push verification stack for CI/CD guardrails?▼

A full pre-push verification stack includes starting the local dev server to verify API availability, running unit and component tests, executing end-to-end tests, and applying security scans with guardrails to surface vulnerabilities or policy violations before merging.

Can I automate local dev server readiness checks and security scans before a git push?▼

Yes, this pre-push verification stack automates local dev server startup, verifies API availability, and includes security scans with guardrails checks to surface vulnerabilities or policy violations before code is pushed.

Does pre-push verification handle sequential test execution and stop on failure?▼

Pre-push verification orchestrates sequential tasks deterministically, running unit tests, E2E tests, and security scans. It handles failures by reporting them immediately and blocking the push from proceeding until remediated.

When do I need to run E2E tests and security scans before pushing to remote?▼

You need to run E2E tests and security scans before pushing to remote when your development workflows require validating core functionality and surfacing vulnerabilities or policy violations prior to merging code changes.