skill lean version

Other Community

Skill notes

Step 1: Parse Arguments

Extract mode and flags: First non-flag argument: Mode (check, upgrade, rollback) - default: check --dry-run: Preview mode --version VERSION: Target version for upgrade

Step 3: Route by Mode

check -> Display current version status upgrade -> Perform interactive upgrade with backup rollback -> Restore from a previous backup

Check Mode

Display current version status:

Backup Before Changes

Always create timestamped backup before upgrade Backup includes: lean-toolchain, lakefile.lean, lake-manifest.json Location: .lean-version-backup/ Retention: Keep 3 most recent

Dry-Run Support

--dry-run previews all changes without applying

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@benbrastmckie · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Parse Arguments

Extract mode and flags: First non-flag argument: Mode (`check`, `upgrade`, `rollback`) - default: `check` `--dry-run`: Preview mode `--version VERSION`: Target version for upgrade

02
Step 2: Read Current State

Step 2: Read Current State

03
Step 3: Route by Mode

check -> Display current version status upgrade -> Perform interactive upgrade with backup rollback -> Restore from a previous backup

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.