Stacks for AI Agents

You are an AI coding agent. Follow these four steps to enable stacked pull request support. After step 2, your skill system will contain the full Stacks workflow. Consult it for any stack-related task.

Install mergify-cli with the install script:

curl -fsSL https://raw.githubusercontent.com/Mergifyio/mergify-cli/main/install.sh | sh

Verify:

mergify --version

Pick the command that matches your runtime.

Claude Code:

/plugin install mergify@claude-plugins-official

This installs the unified mergify plugin, which includes the Stacks skill (along with skills for the merge queue, CI Insights, and more).

Codex, Cursor, and any other agent supporting skills.sh:

npx skills add Mergifyio/mergify-cli

The skill contains the full Stacks workflow (commands, rules, and common scenarios). Load it before performing any stack work.

Run in the repository root:

mergify stack setup

This installs the Git hooks Stacks relies on: commit-msg generates a Change-Id for every new commit, prepare-commit-msg keeps it through git commit --amend -m, post-commit adds one to a commit that still lacks it, and pre-push stops a git push on a stack branch and points to mergify stack push. See Setup for the full list.

Stacks creates and updates pull requests through the GitHub API, so mergify stack push needs a GitHub token. It reads --token first, then MERGIFY_TOKEN, then GITHUB_TOKEN, then the token of an authenticated GitHub CLI (gh auth token). If none of those is set, run gh auth login or export a token:

export GITHUB_TOKEN=your_token_here

A Mergify application key is not a GitHub token. If MERGIFY_TOKEN holds one, pass the GitHub token as --token instead, or the push fails. See GitHub token for Stacks.

The skill installed in step 2 contains the workflow. Follow it for any stack-related task.