pre-merge

Orchestrate pre-merge checks into a comprehensive readiness report.

11|3|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/ImperialAutomation/claude-code-toolkit --skill pre-merge-imperialautomation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-merge
Source: https://github.com/ImperialAutomation/claude-code-toolkit/tree/main/skills/pre-merge
Command: npx skills add https://github.com/ImperialAutomation/claude-code-toolkit --skill pre-merge-imperialautomation

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill consolidates review, testing, verification, and acceptance checks into a single comprehensive report to ensure code quality and readiness before merging.

Core Features & Use Cases

  • Unified Quality Assurance: Coordinates multiple testing and review phases to streamline code validation.
  • Scope Determination: Identifies affected files and branches, facilitating targeted assessments.
  • Informed Decision-Making: Summarizes results for decision makers to approve or flag issues before merge.
  • Use Case: Developers use this Skill to evaluate a pull request, see an aggregated report of code review, tests, runtime health, and acceptance criteria verification, and decide whether to proceed with merging.

Quick Start

Invoke the pre-merge skill with the pull request number or without arguments to analyze current branch and generate a detailed readiness report.

Frequently Asked Questions about pre-merge

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

FAQPage Schema
How do I run comprehensive code review and testing checks before merging a pull request?

To run pre-merge checks, invoke the skill with a pull request number or on your current branch. It orchestrates code review, tests, runtime health, and acceptance criteria into a single readiness report for informed merging decisions.

What is a pre-merge quality gate and how does it validate code integrity?

A pre-merge quality gate validates code integrity by coordinating multiple testing and verification phases. It identifies affected files, runs targeted assessments, and summarizes results to ensure project quality standards are met before merging changes.

Can I use this pre-merge skill to evaluate pull request readiness on my current branch?

Yes, you can evaluate pull request readiness by invoking the skill without arguments to analyze your current branch. It generates a detailed report aggregating code review, tests, runtime health, and acceptance criteria verification.

How do I determine the scope of affected files for targeted CI/CD assessments?

The skill automatically determines scope by identifying affected files and branches within your pull request. This facilitates targeted assessments, streamlining the validation of code changes before generating the final merge readiness report.

What's the best way to consolidate acceptance criteria verification and runtime health checks before a merge?

The best way to consolidate verification checks is using a unified quality assurance process. This skill coordinates review, testing, runtime health, and acceptance phases into one comprehensive report to ensure code readiness before merging.

Does this pre-merge quality gate require any external dependencies to run tests?

No, the pre-merge quality gate operates without external dependencies. It uses internal scripts and references to orchestrate testing, code review, and runtime health checks, generating a consolidated readiness report independently.