fix-mise

Fix Mise

Diagnose, fix, and validate mise runtime failures. Use when commands fail from mise config, missing runtimes, stale pins, trust prompts, or shell activation drift.

Philosophy

• Keep the workflow evidence-first and bounded to the requested scope.
• Prefer the smallest reversible step that proves or disproves the current assumption.
• Preserve user work and repo-native contracts before introducing new machinery.

When To Use

• Resolving untrusted mise config.
• Installing or aligning required runtimes.
• Choosing stable mise exec versus shell activation.
• Cache, data, or state write failures that look like Operation not permitted.
• Updating mise itself or distinguishing it from mise upgrade tool updates.

Avoid

• Unrelated work that belongs to a more specific skill.
• Broad rewrites before the first blocker or decision point is understood.
• Claiming success without command, artifact, or decision evidence.

Inputs

• failing command
• error output
• repo path
• mise config
• expected versions

Outputs

• root cause
• remediation
• verification evidence
• residual risk
• Schema-bound outputs include schema_version.

Workflow

1. Classify the requested mode and collect only the missing critical inputs.
2. Inspect 2-3 focused surfaces before expanding scope.
3. Take the smallest action that advances the confirmed goal.
4. Stop at the first failed gate or blocker and report exact evidence.
5. Rerun the relevant validation after fixes before claiming completion.

Current Mise Triage

• Start with mise doctor, mise --version, which mise, and mise cache path.
• Use mise install for missing tools and mise list to confirm selected versions.
• Use mise trust <path> only for the specific config file or directory causing a trust blocker.
• Use mise cache prune --dry-run before pruning stale cache, then mise cache prune only when cleanup is actually requested.
• Update the mise binary according to its install method: Homebrew-managed installs use brew upgrade mise; non-package-manager installs can use mise self-update --yes.
• Keep mise upgrade for configured tools, not the mise binary itself. Use mise upgrade --dry-run before changing tool versions unless the user explicitly asked for a broad upgrade.