gates

name	gates
description	Use when the current thread needs explicit delivery-gate progression, such as “get this reviewed”, “queue this for merge”, “get this reviewed and merged”, or when you need `mt gate list --templates`, `mt gate list --actionable`, `mt gate add`, or `mt gate request`.

Gates

Use this skill when

• The thread needs to register or progress delivery gates on its current workstream.
• The user asks for review or merge outcomes rather than raw PR creation.
• You need to inspect what gates already exist, what system gates can be added, or what needs action now.

Mental model

• Gates belong to the workstream, but mt gate resolves the current thread's active workstream automatically.
• mt gate add <gate_key> registers durable delivery intent.
• mt gate request <gate_key> progresses an already materialized system gate into its lane.
• Do not assume finishing implementation automatically submits review or merge requests.

Core loop

1. Inspect materialized gates with mt gate list.
2. Discover addable system gates with mt gate list --templates.
3. Materialize needed system gates with mt gate add <gate_key>.
4. Check what currently needs thread action with mt gate list --actionable.
5. Progress a materialized gate with mt gate request <gate_key> once its prerequisites exist.
6. Use mt gate waive ... or mt gate override ... when the thread intentionally bypasses or resolves a gate via human judgment.

V1 system gates

• pr_reviewed: use when the thread should go through Reviewer. Request it only after a bound PR and current head SHA exist.
• pr_merged: use when the thread should go through Merge Queue. Request it only after merge prerequisites are satisfied.

Common flows

Get a PR reviewed:

mt gate list --templates
mt gate add pr_reviewed
mt pr --json   # if the PR does not exist yet
mt gate request pr_reviewed --summary "Please review the current PR"

Get a PR reviewed and merged:

mt gate add pr_reviewed
mt gate add pr_merged
mt gate request pr_reviewed --summary "Please review the current PR"
# After review clears:
mt gate request pr_merged --summary "Queue this PR for merge"

Constraints

• mt gate add is idempotent and should not reset human-locked or terminal gate state.
• Adding a gate is not the same as requesting its handoff.
• Do not use mt gate create or mt gate update to materialize system gates like pr_reviewed or pr_merged.
• mt gate list --actionable is the baseline local view of gates that currently need thread action. Open handoffs generally mean "wait" rather than "blindly request again".

Related

• Use mighty/delivery/SKILL.md when the missing step is PR creation or artifact registration.
• Use mighty/get-pr-reviewed/SKILL.md for the review-specific pointer flow.
• Use mighty/merge-pr/SKILL.md for the merge-specific pointer flow.