/version-iloom
Update version number and license date for iloom releases. Updates LICENSE and README.md dates, then runs pnpm version.
$ npx -y skills add iloom-ai/iloom-cli --skill version-iloom --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/version-iloom
Context preview
The summary Claude sees to decide when to auto-load this skill.
Update version number and license date for iloom releases. Updates LICENSE and README.md dates, then runs pnpm version.
SKILL.md
version-iloom.SKILL.mdname: version-iloom
description: Update version number and license date for iloom releases. Updates LICENSE and README.md dates, then runs pnpm version.
disable-model-invocation: true
argument-hint: [patch|minor|major]
allowed-tools: Bash, Edit, Read
Version Iloom
Update the iloom version and license change date for a release.
Arguments
Version bump type: `$ARGUMENTS` (defaults to `patch` if empty)
License Date
The new license change date (4 years from today): !`date -v+4y "+%Y-%m-%d"`
Task
1. **Update LICENSE file** (line 23): Change the `Change Date:` value to the license date shown above 2. **Update README.md** (line 527): Change the date in "Converts to Apache 2.0 on YYYY-MM-DD" to the license date shown above 3. **Commit date changes**: Stage and commit LICENSE and README.md with message "Update license change date to YYYY-MM-DD" 4. **Run version bump**: Execute `npm version $ARGUMENTS --no-git-tag-version` (use `patch` if no argument was provided), then commit the package.json change with the version number as the message 5. **Squash commits**: Run `git reset --soft HEAD~2 && git commit --no-verify -m "X.Y.Z"` to squash into one commit (use the new version number as the message) 6. **Create version tag**: Run `git tag vX.Y.Z` to create the tag on the squashed commit 7. **Report**: Show the old and new version numbers
Important
- Use `npm version` with `--no-git-tag-version` to avoid creating the tag before squashing
- The date format must be `YYYY-MM-DD`
Read more
name: version-iloom description: Update version number and license date for iloom releases. Updates LICENSE and README.md dates, then runs pnpm version. disable-model-invocation: true argument-hint: [patch|minor|major] allowed-tools: Bash, Edit, Read
Version Iloom
Update the iloom version and license change date for a release.
Arguments
Version bump type: `$ARGUMENTS` (defaults to `patch` if empty)
License Date
The new license change date (4 years from today): !`date -v+4y "+%Y-%m-%d"`
Task
1. **Update LICENSE file** (line 23): Change the `Change Date:` value to the license date shown above 2. **Update README.md** (line 527): Change the date in "Converts to Apache 2.0 on YYYY-MM-DD" to the license date shown above 3. **Commit date changes**: Stage and commit LICENSE and README.md with message "Update license change date to YYYY-MM-DD" 4. **Run version bump**: Execute `npm version $ARGUMENTS --no-git-tag-version` (use `patch` if no argument was provided), then commit the package.json change with the version number as the message 5. **Squash commits**: Run `git reset --soft HEAD~2 && git commit --no-verify -m "X.Y.Z"` to squash into one commit (use the new version number as the message) 6. **Create version tag**: Run `git tag vX.Y.Z` to create the tag on the squashed commit 7. **Report**: Show the old and new version numbers
Important
- Use `npm version` with `--no-git-tag-version` to avoid creating the tag before squashing
- The date format must be `YYYY-MM-DD`
iloom: a developer workflow system delivered as a CLI and a VS Code extension for structured AI-assisted development. The CLI is the system of record, running tasks in isolated workflows and persisting analysis, plans, and decisions to your issue tracker, while the VS Code extension exposes insights, assumptions, risks, and decisions in real time.