Generate release changeset files from Git commits and user input.
npx skills add https://github.com/jant-me/jant --skill release-jant-me
Please help me install this Agent Skill. Skill: release Source: https://github.com/jant-me/jant/tree/main/.agents/skills/release Command: npx skills add https://github.com/jant-me/jant --skill release-jant-me
This Skill automates the creation of release changesets for the Jant project, streamlining the process of versioning and releasing new versions of the @jant/core package and create-jant using the repository's fixed-version workflow.
@jant/core and create-jant based on unreleased commits.release command to create a release changeset for the current work.Use the release skill to create a release changeset for the Jant project.
High-intent search queries and answers about installing and using this skill.
Automate changeset creation by using a script that reads unreleased Git commits and prompts for version bumps to generate changeset files. This streamlines package versioning by integrating repository history directly into the release workflow.
A release changeset is a file that documents version bumps and unreleased changes for a package. You need it in software development when utilizing a fixed-version workflow to prepare new releases for packages like @jant/core.
Generate release changesets by executing a command that analyzes your Git history for unreleased commits. The script then uses user input to specify version bumps and creates the corresponding changeset files.
Yes, you need Git repository access and the ability to execute Git commands to create release changesets. The process relies on reading repository history to accurately version and document unreleased changes.
Yes, you can specify version bumps manually. The changeset creation process uses user interaction to allow you to define the version increments and provide a summary of the unreleased commits.
Fixed-version workflows for changeset creation are limited to specific packages like @jant/core and create-jant. They require a Git repository and apply only to development workflows where automated release processes and fixed versioning are necessary.
realsigridjinCreate atomic Git commits with conventional formatting and manage repository history.
kjfsmIdentify affected packages and create pnpm changeset records for npm releases.
maschadAutomate pre-commit quality checks and semantic commits across multi-language repositories.
sgcarstrendsGenerate CHANGELOG.md from conventional commits using semantic-release.