AI Marketplaces Leaderboard

Mergify

ChatGPT plugin

Run and debug your merge queue

View in ChatGPT directory
Featured
No

not on the featured shelf

Movement

From our daily snapshots over the last 30 days.

Rank by placement

#5356of 6,022024h—7d
#5,325#5,419#5,513#5,607Sep 13Sep 19Sep 25Oct 1Oct 7Oct 12

Rank in Developer tools

#480of 537024h—7d
#479#481#483#485Sep 13Sep 19Sep 25Oct 1Oct 7Oct 12

In its category

How this plugin compares with others in the same category. Positions are counted within the category, not across the whole directory.

Developer tools480th of 537 by placement
#PluginPosition7d
477Servotab#5333—
478RAG & GenAI Copilot#5338—
479ECZ-ID DORA Readiness#5351—
480MergifyThis page#5356—
481CRIADOR / Reef#5369—
482Recurse#5370—
483SSOT Check#5376—

All 537 Developer tools plugins

Mergify serializes merges through a queue that runs CI on temporary merge commits, so a pull request that only breaks in combination with another one gets caught before it reaches your default branch. These skills drive the Mergify CLI so an agent can work that queue with you.

Ask why a pull request left the queue and get the engine's own dequeue reason, the checks that failed, and a link straight to the job log. Read the activity log for one pull request or for the whole repository. Validate a .mergify.yml against the schema before you commit it, or simulate what your rules would do on a real pull request. Set up merge protections such as dependencies between pull requests or scheduled freezes for a release window. Turn a branch of commits into a stack of one pull request per commit and keep them rebased.

Six skills ship in the bundle: mergify-merge-queue, mergify-events, mergify-config, mergify-merge-protections, mergify-ci, and mergify-stack.

It runs on the Mergify CLI, a single static binary with no runtime to install, so it needs a local execution environment: Codex, or ChatGPT desktop with local execution. You need a GitHub repository with Mergify enabled. Install the CLI with 'brew install mergifyio/tap/mergify-cli', sign in once with 'mergify auth login' or set MERGIFY_TOKEN, then ask for what you want in plain language.

Example prompts

  • “Why did pull request #1234 leave the merge queue?”

Skills

  • mergify-ci

    Use Mergify CI commands to upload JUnit test results, detect git references, manage CI scopes, and retrieve merge queue metadata. ALWAYS use this skill when working with CI pipelines, test result uploads, quarantine, scopes detection, or merge queue CI context. Triggers on CI, JUnit, test results, quarantine, scopes, git refs, CI insights.

  • mergify-config

    Use Mergify config commands to validate configuration files, simulate Mergify actions, and write Mergify configuration. ALWAYS use this skill when validating, writing, editing, or simulating Mergify config. Triggers on config validate, config simulate, mergify configuration, mergify.yml, .mergify.yml, merge queue config, workflow rules, conditions.

  • mergify-events

    Use `mergify events` to browse the Mergify activity log — every event Mergify recorded for a repository or one pull request (queue enters/leaves, merges, commands, CI Insights, freezes), as a human timeline or JSON. ALWAYS use this skill when investigating what Mergify did to a PR or repository and when, reconstructing a pull request's merge-queue lifecycle, auditing Mergify actions, or filtering events by type. Triggers on activity log, event log, events, what did Mergify do, queue lifecycle, queue history, event timeline, event_type, action.queue.

  • mergify-merge-protections

    Use Mergify merge protections to control when PRs merge — PR dependencies (Depends-On header), delayed merges (Merge-After header), and scheduled freezes (CLI). ALWAYS use this skill when managing merge freezes, deployment windows, temporarily blocking merges, setting up PR dependencies, blocking a PR on another PR, coordinating cross-repo merges, scheduling a merge for a specific time, or adding Depends-On or Merge-After headers to PRs. Triggers on freeze, scheduled freeze, merge freeze, deployment freeze, halt merges, depends on, dependency, block merge, merge after, merge later, schedule merge, delayed merge, cross-repo, merge protection.

  • mergify-merge-queue

    Use Mergify merge queue to queue/dequeue PRs, to monitor and inspect the queue, and to diagnose a dequeued PR — whether it is queued, why it was dequeued, where its CI failure is, and what to do next. ALWAYS use this skill when queuing or dequeuing a PR, checking queue status, investigating PR merge state, finding out why a PR left the queue, pausing/unpausing the queue, or debugging merge failures. Triggers on queue a PR, requeue, dequeue, dequeued, why was my PR dequeued, dequeue reason, merge queue, queue status, queue pause, queue show, pause, unpause, frozen, bisecting, batch, CI checks, CHECKS_FAILED, PULL_REQUEST_UPDATED.

  • mergify-stack

    Use Mergify stacks for git push, commit, branch, and PR creation. ALWAYS use this skill when pushing code, creating commits, creating branches, or creating PRs. Triggers on push, commit, branch, PR, pull request, stack, stacked, git, rebase, checkout, reorder, move, sync, amend, note, revision history.

Categories
Made by
Mergify · Website
Sign-in
On Install
Capabilities
Interactive, Read, Write
Availability
Available
Version
1.0.0
Keywords
git, pr, stacked-prs, merge-queue, ci, test-insights, flaky-tests, quarantine, freeze, config, push, commit, branch, rebase, checkout, workflow
Created
September 17, 2026
More info