validate-before-merge

Name: validate-before-merge
Availability: InStock
Author: cartridge-gg

Run lint, build, and test checks before merging code.

80|49|Updated Mar 27, 2022

Search Tags:#workflow #validation #build #lint #ci #tests #pre-merge

Ready to run

npx skills add https://github.com/cartridge-gg/controller --skill validate-before-merge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: validate-before-merge
Source: https://github.com/cartridge-gg/controller/tree/main/.agents/skills/validate-before-merge
Command: npx skills add https://github.com/cartridge-gg/controller --skill validate-before-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill runs all checks that CI performs to validate code is ready for merge. Use this to catch issues locally before CI runs.

Core Features & Use Cases

Lint and format validations
Build and test orchestration
Quick local pre-merge validation workflow

Quick Start

Run the full validation locally to ensure lint, build, and tests pass before merging.

Frequently Asked Questions about validate-before-merge

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

FAQPage Schema

How do I run pre-merge validation checks locally before opening a PR?▼

Pre-merge validation runs lint, build, and test checks on code changes locally. It executes pnpm lint:check, pnpm build, and pnpm test:ci to catch issues and ensure a clean, ready-to-merge state before CI.

What is the best way to automate lint and build checks for local development workflows?▼

Automating local development validation involves running pnpm lint:check and pnpm build commands. This orchestrates lint and format validations quickly, providing rapid feedback on code readiness before merging.

Does this pre-merge validation skill support UI checks alongside tests?▼

Yes, pre-merge validation supports optional UI checks alongside required test orchestration. It runs pnpm test:ci and applies optional UI checks to enforce a clean, ready-to-merge state for your code changes.

Why should I run local CI checks instead of waiting for remote build validation?▼

Running local CI checks catches issues before remote CI runs, saving time. It validates code readiness by applying the same lint, build, and test checks locally, ensuring rapid feedback on merge readiness.

Can I use pnpm to orchestrate test and build validation for code readiness?▼

Yes, you can use pnpm to orchestrate test and build validation. The workflow runs pnpm build, pnpm test:ci, and pnpm lint:check to enforce required checks and validate code readiness before merging.