メニュー
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.
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 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.
Upload files and reference them correctly in Mighty specs/tasks/decisions. Use when asked to attach screenshots, logs, PDFs, or other file artifacts and ensure they are represented in both rich text and graph evidence links.
| name | delivery |
| description | 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. |
Treat the deliverable as a workstream-owned artifact. For GitHub PRs, the happy path is mt pr; use mt artifact create only when the PR already exists and Mighty needs a matching artifact record. Once the PR exists, use mighty/gates/SKILL.md to add and request pr_reviewed / pr_merged explicitly.
For repo changes that should merge through GitHub:
mt pr.mt pr --json when a later agent step needs the PR URL, number, artifact id, or artifact ref.Examples:
mt pr --title "Fix artifact-backed PR persistence" --body-file -
mt pr --draft --fill
mt pr --json
What mt pr handles:
gh pr creategithub_pr artifact with create-time metadataAfter mt pr, switch to mighty/gates/SKILL.md when the user wants review or merge outcomes:
mt gate add pr_reviewed
mt gate request pr_reviewed --summary "Please review the current PR"
Use mt artifact create when the external artifact already exists and you need to author the matching artifact record directly.
GitHub PR example:
mt artifact create \
--type github_pr \
--ref github:repo-selector:acme/repo:pr:77 \
--pull-number 77 \
--html-url https://github.com/acme/repo/pull/77 \
--head-ref feature/queue \
--head-sha abc1234 \
--base-ref main \
--draft false \
--json
Use --workstream-id <id> when you have the owning workstream id available and need to attach ownership explicitly.
mt pr over raw gh pr create when you want the PR artifact persisted automatically.mt pr --json over scraping human-readable command output.mighty/gates/SKILL.md after PR creation when the thread needs explicit review or merge progression.mt link for evidence edges and citations; use mt artifact create for first-class artifact records.--body-file - or --body-file <path>.