Menú
Use `mt rebase` to rebase the current branch onto `origin/<base>`, especially in shallow sandbox checkouts.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
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.
Basado en la clasificación ocupacional SOC
| name | rebase |
| description | Use `mt rebase` to rebase the current branch onto `origin/<base>`, especially in shallow sandbox checkouts. |
Use this when the current branch needs the latest origin/main (or another base branch), especially inside Mighty sandboxes that start from a shallow checkout.
Confirm the worktree is clean:
git status --shortRun the narrow helper:
mt rebasemt rebase --base <branch>If git reports conflicts, resolve them with normal git rebase flow:
git statusgit rebase --continuegit rebase --abortIf you need the rewritten branch on the remote, push it yourself:
git push --force-with-leasemt rebase widens shallow history before ancestry-aware git operations.origin remote in this scope.mt prime if you lost context and keep using mt commands rather than stale SHAs to recover the current workstream state.mt pr separately after the branch is ready..mighty relink state, mt rebase auto-commits those changes.