athola/version-updates
plugins/sanctum/skills/version-updates/SKILL.md
Bumps versions, updates changelogs, and coordinates version changes across files for releases. Use when preparing a release or bumping the project version.
$ install --global
skillsauthnpx skillsauth add athola/claude-night-market version-updatesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 30, 2026, 4:10 AM131.0s1 file scanned
SKILL.md
- name:
- version-updates
- description:
- Bumps versions, updates changelogs, and coordinates version changes across files for releases. Use when preparing a release or bumping the project version.
- alwaysApply:
- false
- category:
- artifact-generation
- tools:
- []
- complexity:
- medium
- model_hint:
- standard
- estimated_tokens:
- 700
- - sanctum:
- git-workspace-review
Version Update Workflow
When To Use
Use this skill when preparing a release or bumping the project version.
Run Skill(sanctum:git-workspace-review) first to capture current changes.
When NOT To Use
- Just documentation updates - use doc-updates
- Full PR preparation - use pr-prep
Required TodoWrite Items
version-update:context-collectedversion-update:target-filesversion-update:version-setversion-update:docs-updatedversion-update:verification
Step 1: Collect Context (context-collected)
- Confirm which version to apply (default: bump patch).
- If the prompt provides an explicit version, note it.
- validate
Skill(sanctum:git-workspace-review)has already captured the repository status.
Step 2: Identify Targets (target-files)
- Find ALL configuration files that store versions using recursive search:
- Root level:
Cargo.toml,package.json,pyproject.toml - Nested directories: Use glob to find
*/pyproject.toml,*/Cargo.toml,*/package.json - Example:
plugins/memory-palace/hooks/pyproject.tomlmust be included - Exclude virtual environments (
.venv,node_modules,target/) using grep -v
- Root level:
- Include changelog and README references that mention the version.
- Use:
find plugins -name "pyproject.toml" -o -name "Cargo.toml" | grep -v ".venv"
Step 3: Update Versions (version-set)
- Automated approach: Use
plugins/sanctum/scripts/update_versions.py <version>to update all version files- Supports pyproject.toml, Cargo.toml, package.json
- Automatically excludes virtual environments
- Finds nested version files (e.g.,
plugins/memory-palace/hooks/pyproject.toml) - Use
--dry-runflag first to preview changes
- Manual approach: Update each target file with the new version
- For semantic versions, follow
MAJOR.MINOR.PATCHor the specified format - If the project supports multiple packages, document each update
- For semantic versions, follow
Step 4: Update Documentation (docs-updated)
- Add or update changelog entries with today's date.
- Refresh README and docs references to mention the new version and any release notes.
Critical Documentation Files with Version References
These files contain version numbers and MUST be checked during version bumps:
| File | Content |
|------|---------|
| docs/api-overview.md | Plugin inventory table with all plugin versions |
| CHANGELOG.md | Version history and release notes |
| book/src/reference/capabilities-reference.md | May reference version-specific features |
| Plugin READMEs | May mention plugin versions |
Scan for Additional Version References
# Find all docs mentioning the OLD version
grep -r "1\.2\.6" docs/ book/ --include="*.md" | grep -v node_modules
# Common patterns to search:
# - "v1.2.6", "1.2.6", "(v1.2.6)"
# - Version tables in markdown
# - "Added in X.Y.Z" annotations
Update Sequence
- Update config files (pyproject.toml, plugin.json, etc.) - automated
- Update
CHANGELOG.md- add new version section - Update
docs/api-overview.md- update version table and plugin details - Scan for other version references and update as needed
Step 5: Verification (verification)
- Run relevant builds or tests if version bumps require them (e.g.,
cargo test,npm test). - Show
git status -sbandgit diffexcerpts to confirm the version bumps.
Output Instructions
- Summarize the files changed and the new version number.
- Mention follow-up steps, such as publishing or tagging, if applicable.
Related Skills
athola/friction-detector
tools
VerifiedTrustedCommunity
Detect friction signals; graduate patterns into rules. Use for session retrospectives.
300SKILL.mdUpdated Apr 23, 2026
athola/validate-mr
testing
VerifiedTrustedCommunity
Use when you need a diff-derived test plan for an MR — reads the diff, groups changes by area, runs targeted verifications, and proves revert-tests are genuine guards, not dead assertions.
294SKILL.mdUpdated May 30, 2026
athola/palace-index-curator
development
VerifiedTrustedCommunity
Curate the web-capture index. Use when the capture backlog grows, captures sit unprocessed at seedling/pending, or to surface stored research during work.
294SKILL.mdUpdated May 30, 2026
athola/memory-clarity-probe
testing
VerifiedTrustedCommunity
Probe memory/summary clarity via dual anchor questions: task progress, info gaps. Use when verifying session state or summary before handoff or compression.
294SKILL.mdUpdated May 30, 2026