Automates the release cycle for n98-magerun2, including versioning, changelog updates, and release triggering.
Install
mkdir -p .claude/skills/magerun-release && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3168" && unzip -o skill.zip -d .claude/skills/magerun-release && rm skill.zipInstalls to .claude/skills/magerun-release
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Technical release process for n98-magerun2Key capabilities
- →Analyze git logs for release changes
- →Update application version files
- →Generate changelog from git history
- →Execute release-it workflow
How it works
The process involves identifying changes from git logs, updating version numbers in source files and documentation, and running the release-it tool to finalize the release.
Inputs & outputs
When to use magerun-release
- →Bump project version number
- →Generate changelog from git history
- →Execute final release workflow
About this skill
magerun-release
This skill describes the technical release process of the n98-magerun2 tool.
When to use
Use this skill when a new version of n98-magerun2 needs to be released.
Instructions
To release a new version, follow these steps:
- Investigate the git log to find all changes.
- Tool:
git log $(git describe --tags --abbrev=0)..HEAD --oneline
- Tool:
- Determine the next version number.
- Follow semantic versioning (SemVer).
- Update the
\N98\Magento\Application::APP_VERSIONwith the new version number.- File:
src/N98/Magento/Application.php
- File:
- Update the
version.txtwith the new version number.- File:
version.txt
- File:
- Update the
CHANGELOG.mdwith the new version number.- File:
CHANGELOG.md - Ensure all changes from the git log are documented.
- File:
- Run
release-ittool.- Command:
npx release-it(orvendor/bin/release-itif available via composer, but typically it's a JS tool). - Ask the user to confirm the release process and follow the prompts to complete the release. The release-it call has to be done in the
masterbranch.
- Command:
When not to use it
- →When not on the master branch
Limitations
- →Requires manual confirmation of release prompts
- →Must be executed on the master branch
How it compares
It follows a specific technical release process for n98-magerun2 rather than a generic version bump.
Compared to similar skills
magerun-release side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| magerun-release (this skill) | 1 | 5mo | No flags | Intermediate |
| release-minor | 1 | 2mo | No flags | Intermediate |
| laravel-zero-cli | 0 | 4mo | No flags | Intermediate |
| github-release-management | 4 | 6mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
release-minor
knuckleswtf
Automates the process of tagging a new minor release for Scribe by analyzing commit messages, updating the changelog, and creating a GitHub release.
laravel-zero-cli
ChaDonSom
Core workflows for the Black Labs Laravel Zero CLI (build, test, lint, release helpers)
github-release-management
ruvnet
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management
agent-release-swarm
ruvnet
Agent skill for release-swarm - invoke with $agent-release-swarm
release
ziggy42
Use this skill when the user wants to cut a new release.
release-branch
mono
Create a release branch for SkiaSharp. Use when user says "release X", "start release X", "create release branch for X", "I want to release", or "release now". This is the FIRST step of releasing - creates branch and pushes to trigger CI. Can auto-detect next preview version from main branch.