skills.rest
HabibTorjmen
HabibTorjmenCOMMUNITY
Explore all skills by this author →
GitHub

merge-trains

Route pull requests into merge-train branches and integrate them into `next` with correct squashing and CI behavior.

Updated May 14, 2026
Search Tags:#automation#github#pull requests#ci#release engineering#branch strategy#merge trains
One-click install
npx skills add https://github.com/HabibTorjmen/Blockchain --skill merge-trains
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-trains
Source: https://github.com/HabibTorjmen/Blockchain/tree/main/aztec-packages/.claude/skills/merge-trains
Command: npx skills add https://github.com/HabibTorjmen/Blockchain --skill merge-trains

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents delays and CI failures by guiding contributors on how to correctly target and integrate changes using repository merge trains instead of competing directly against the next branch.

Core Features & Use Cases

  • Correct merge-train targeting: Create feature branches from the specified merge-train base branch (driven by CI_BASE_BRANCH) and open PRs against the right merge-train/* branch.
  • Accurate squashing and merge semantics: Ensures your PRs are squash-merged into the train while the train-to-next merge preserves individual commits via a merge commit (with ci-no-squash behavior).
  • CI modes and failure handling: Explains how specialized CI runs for specific trains, how merge-queue modes apply, and what to do when the merge-train PR fails or auto-merge is blocked.
  • Bypass checks safely: Provides a guarded procedure for applying ci-skip and using GitHub bypass merge only when explicitly requested and confirmed.

Quick Start

Ask me how to create a PR targeting the correct merge-train/* base branch for your change, and what to do if the merge-train CI fails.

Frequently Asked Questions about merge-trains

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

FAQPage Schema
How do I target the correct merge-train base branch when opening a GitHub pull request?▼

To target a merge-train correctly, create your feature branch from the specified merge-train base branch driven by `CI_BASE_BRANCH` and open your PR against the matching `merge-train/*` branch instead of `next`.

What is the correct merge strategy for integrating pull requests into a merge train?▼

The correct merge strategy squash-merges your pull requests into the merge train, while the train-to-`next` integration preserves individual commits using a merge commit with `ci-no-squash` behavior.

Why does my merge-train CI fail and how should I handle the failure?▼

Merge-train CI failures occur when specialized CI runs for specific trains or merge-queue modes encounter issues. Follow prescribed failure procedures to resolve the errors or unblock auto-merge.

Can I bypass CI checks on a merge-train pull request?▼

You can bypass CI checks on a merge-train pull request by applying `ci-skip` and using GitHub bypass merge, but only when explicitly requested and confirmed through the guarded procedure.

When should I use a merge train instead of opening a PR directly against the next branch?▼

Use a merge train instead of opening a PR directly against the `next` branch when your team relies on `merge-train/*` batching and merge-queue execution to coordinate domain-specific changes and prevent CI delays.

Related Skills

Explore More Software Engineering Skills→
shellicarshellicar

github-repos

Configure GitHub repository settings and enforce branch protection rules via the gh CLI.

Community
Intermediate
HabibTorjmenHabibTorjmen

merge-train-infra

Document GitHub Actions automation internals for merge-train operations.

Community
Advanced
jankneumannjankneumann
4

merge-pull-requests

Triage and merge open pull requests from multiple sources.

Community
Advanced
badbsallyybadbsallyy

merge-pr

Merge GitHub pull requests via squash and clean up worktrees.

Community
Advanced