lean-update
Installation
SKILL.md
lean-update
Ground rules
- Standalone. Standalone skill: use the current request or explicit arguments. Read applicable project instructions and only task-relevant context.
- No prerequisites. No Lean installation, CLI, configuration or companion skill is required; do not install a workflow or create workflow files as prerequisites. Existing project rules apply.
- Depth. Use requested procedure depth, or standard by default. High adds relevant boundary cases and stronger evidence; ultra adds cross-part consistency and contradictory evidence where relevant. Depth does not change model reasoning settings.
- Records. Keep decisions in conversation unless a suitable project record exists or the user requests persistence.
- Scope. This updates skills, not a project runtime.
- Source. Source: https://github.com/aussadawut-dev/lean-skills. It works when only this skill is installed.
Input and result
- Input. Input is the requested collection or named skills, source and installation scope, reusing verified metadata.
- READY. Preview concludes READY with a pinned, concrete plan and performs no installation.
- DONE. Update concludes DONE only when every requested addition/update is validated; report unchanged items, source revision, destinations and recovery evidence.
- BLOCKED. Conflicts, uncertain provenance or unavailable prerequisites are BLOCKED for the affected items even when independent updates succeed.
- FAILED. A failed operation is FAILED if the requested result remains unmet; report whether restoration succeeded, failed or is uncertain. A successful rollback does not turn a failed update into DONE.