菜单
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`.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Upload local screenshot/video artifacts from agent runs and return renderable file embeds (`![[file ...]]`) plus `mighty-file:` refs for thread UI previews.
Use when the user uploads files or a .zip archive (like user research or logs). Describes how to locate attached files in the sandbox, extract archives if necessary, synthesize findings, and save results back to Mighty.
Record durable architectural or policy choices with `mt decision`. Use when choosing between alternatives, setting lasting constraints, superseding an accepted decision, or capturing significant rationale while context is fresh.
Use when a workstream needs a reviewable deliverable, especially a GitHub PR. Covers `mt pr` for the normal PR-backed path, `mt artifact create` for existing deliverables, and the workstream delivery contract that hands PRs into review and merge gates.
Use when asked to write, migrate, or organize long-form Mighty docs, or decide whether something should be a doc or a spec/task/decision. Covers `mt doc` authoring, doc types, and when guides or runbooks should live in the Mighty graph instead of standalone repo markdown.
Use Mighty-native eval primitives from external repos. Covers the native eval record model, local or hosted write-back flows, and when to reach for the deeper `external-evals` skill for framework-specific mapping.
| 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`. |
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.mt gate list.mt gate list --templates.mt gate add <gate_key>.mt gate list --actionable.mt gate request <gate_key> once its prerequisites exist.mt gate waive ... or mt gate override ... when the thread intentionally bypasses or resolves a gate via human judgment.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.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"
mt gate add is idempotent and should not reset human-locked or terminal gate state.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".mighty/delivery/SKILL.md when the missing step is PR creation or artifact registration.mighty/get-pr-reviewed/SKILL.md for the review-specific pointer flow.mighty/merge-pr/SKILL.md for the merge-specific pointer flow.