Release automation
Automate complete release process with versioning and publishingFrom its SKILL.md
npx -y skills add manastalukdar/ai-devstudio --skill release-automationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 219 tokens by cl100k_base, as published. Nobody here has run it
Release Automation
I'll automate your complete release process: version bumping, changelog generation, git tagging, release creation, and package publishing.
Arguments: $ARGUMENTS - version number (e.g., 1.2.0, major, minor, patch) or release type
Release Philosophy
- Semantic Versioning: Proper MAJOR.MINOR.PATCH versioning
- Automated Changelog: Generated from conventional commits
- Safe Defaults: Validate before publishing
- Platform Agnostic: Support npm, PyPI, Go modules, Ruby gems, Cargo, Maven
Token Optimization
Expected range: 800–2,500 tokens (initial), 100 tokens (clean state)
Caching: Caches package info in .claude/cache/release-automation/package-info.json for 7 days. Invalidated when package.json changes.
Early exit: Returns immediately if the working tree is not clean.
Patterns used: Grep-before-Read, early exit, Bash for system queries, caching
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most automation workflows skills give in 219 tokens
Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-07
- Write conventional commit messagesin 36 of 745, across 35 files
- Delete branches after mergein 30 of 745, across 21 files
- Make atomic commitsin 25 of 745, across 15 files
- Write minimal code to pass testsin 22 of 745, across 10 files
- Re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
- Use try-catch for error handlingin 20 of 745, across 8 files
- Run tests before committingin 20 of 745, across 12 files
- Write tests before implementationin 20 of 745, across 8 files
- Configure branch protection rulesin 19 of 745, across 5 files
- Explain the why in commit messagesin 19 of 745, across 9 files
- Refactor code while tests remain greenin 19 of 745, across 6 files
- Interact with elements using refsin 19 of 745, across 11 files
Said here and by no other author read
- generate changelog from conventional commits
- validate before publishing
- support multiple package platforms
- cache package information for seven days
- invalidate cache when package file changes
- return immediately if working tree is unclean
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.