Menú
Resolve `.mighty/loro/*.loro` merge conflicts safely using `mt merge`, then verify store health and sync.
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.
Basado en la clasificación ocupacional SOC
Optimize a pydantic-ai agent's instructions, tool descriptions, output type, and signature inputs using the gepa CLI. Trigger when the user asks to "optimize this agent", "improve tool descriptions", iterate on prompts driven by eval failures, or otherwise improve a pydantic-ai agent against a dataset. Operates in the user's repo with full filesystem access — YOU are the reflection model; the gepa CLI handles minibatches, evaluation, and Pareto bookkeeping.
Use the `mt` tool to work with this repo’s Mighty graph: run `mt prime` at session start; prefer `mt search`/`mt tree`/`mt show` before reading code; create specs/decisions/tasks and link evidence; triage `mt inbox`; and close out with `mt closeout` then `mt commit`. For full workflow + templates, run `mt prime`.
Plan work using Mighty (mt) by creating/updating specs and recording decisions, then spawning/structuring implementation tasks. Use when asked to plan/outline/break down a change, draft a spec (feature/rule/invariant/bug), record an ADR-style decision, or turn a fuzzy request into a structured Mighty spec tree with linked tasks.
Audit and migrate specs to the Guarantees + Constraints format. Use when asked to review spec quality, find non-conforming specs, or batch-migrate specs from the old Behaviors/Interfaces format.
Track and execute implementation work using Mighty (mt) tasks, with progress comments, linked evidence, recorded decisions, and clean closeout. Use when asked to fix a bug, implement a feature/refactor, or “work through” changes in code while keeping Mighty tasks/specs/decisions updated.
Convert roman numerals to integers.
| name | mighty-merge |
| description | Resolve `.mighty/loro/*.loro` merge conflicts safely using `mt merge`, then verify store health and sync. |
Use this when git reports conflicts in .mighty/loro/*.loro files.
Confirm what’s conflicted:
git statusgit diff --name-only --diff-filter=UUse Mighty’s merge helper (preferred):
mt merge (merges all unresolved .mighty/loro/*.loro conflicts)mt merge .mighty/loro/edges/<file>.loro ... (merge specific files)Re-check health:
mt doctorCommit and sync:
mt commit (commits .mighty/ changes)git push.loro conflicts by hand; they are binary CRDT snapshots. Use mt merge.mt merge can’t resolve a conflict, keep the work unblocked: capture details in an issue comment and mark the blocking item appropriately.