pre-merge-check

Name: pre-merge-check
Availability: InStock
Author: aramark-destinations

Orchestrate lint, tests, and block audits before merging pull requests.

Updated Aug 27, 2026

Search Tags:#quality-gate #lint #ci #pull-request #tests #block-audit

Ready to run

npx skills add https://github.com/aramark-destinations/aramark-mb --skill pre-merge-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pre-merge-check
Source: https://github.com/aramark-destinations/aramark-mb/tree/main/.agents/skills/eds/pre-merge-check
Command: npx skills add https://github.com/aramark-destinations/aramark-mb --skill pre-merge-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a final set of quality checks for a PR by coordinating linting, tests, and block audits prior to merge.

Core Features & Use Cases

Orchestrates checks from multiple skills (e.g., eds/block-audit, eds/quality-audit) to validate changes.
Applies to PRs across blocks, brands, styles to ensure consistent quality and compliance.
Provides a clear pass/fail gate with actionable feedback for developers.

Quick Start

Trigger the pre-merge-check on the current PR to run all quality gates before merging.

Frequently Asked Questions about pre-merge-check

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

FAQPage Schema

How do I run automated quality gates on a pull request before merging?▼

Automated quality gates on a pull request are executed by orchestrating lint, tests, and block audits before merge. This ensures compliance and reliability across all blocks, brands, and styles during your code review.

What is a PR quality gate and how does it validate my code changes?▼

A PR quality gate validates code changes by coordinating linting, tests, and block audits prior to merge. It applies to all pull requests across blocks, brands, and styles to ensure consistent quality and compliance.

Can I use pre-merge checks to enforce lint coverage and test success across multiple brands?▼

Yes, pre-merge checks enforce lint coverage and test success across multiple brands, styles, and blocks. The quality gate applies to all pull requests and provides a clear pass or fail outcome with actionable feedback.

What's the best way to automate block audits and token validations during a CI workflow?▼

Automating block audits and token validations during a CI workflow is handled by orchestrating these checks as a final quality gate before merge. It satisfies requirements for audit execution and token validations across all pull requests.

Why do I need a final quality gate if I already run lint and tests separately?▼

A final quality gate is needed to orchestrate lint, tests, and block audits together, providing a clear pass or fail gate with actionable feedback. This guarantees compliance and reliability before merge across all blocks and brands.

Does the pre-merge quality gate work with existing block audit and quality audit skills?▼

Yes, the pre-merge quality gate works with existing block audit and quality audit skills by orchestrating their checks to validate changes. It coordinates these skills to ensure consistent quality and compliance prior to merge.