Agent Skills
The repository ships universal agent skills — instructions that teach an AI coding agent how to set up and use Simple Release in your project. They are compatible with Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, and other agents that support the skills format.
setup-simple-release-action
Section titled “setup-simple-release-action”The setup-simple-release-action skill sets up the GitHub Action in a repository end to end. Rather than pasting a template, the skill guides the agent to:
- Detect the project type from the repository — lock files, workspace manifests,
action.yml— and describe it in the config with a version-pinned addon query. You can also just tell the agent what to use. - Fill the workflow from your toolchain — the Node.js version, the package manager and its version, the default branch, and the npm registry are read from the repository, not assumed; the release job publishes with an npm token or through trusted publishing, as you choose.
- Add the optional flows on request — manual release, snapshot release, and maintenance branches. By default only the main release automation flow is set up; if you have not said what you need, the agent asks once.
- Finish with a checklist of the settings only you can change — allowing GitHub Actions to create pull requests, the
NPM_TOKENsecret or the trusted publisher registration, squash merging for release pull requests.
Install the skill into your project with either package runner:
pnpx skills add TrigenSoftware/simple-release --skill setup-simple-release-actionnpx skills add TrigenSoftware/simple-release --skill setup-simple-release-actionsimple-release-action
Section titled “simple-release-action”The simple-release-action skill is the companion for repositories where the action is already set up — it teaches the agent to operate the release flow day to day:
- Ship the regular release — find the release pull request, check its title, squash-merge it with the GitHub CLI, and follow the release run to the tag, the package, and the GitHub release.
- Reshape the pending release — post
!simple-release/set-optionsand!simple-release/set-preamblecomments the way the action honors them: at the very start of the comment, from a collaborator account, with a validjsonblock, and as a new comment rather than an edit. - Run the optional flows — manual releases and snapshots with
gh workflow run, and fixes for previous majors on maintenance branches — after reading from the workflows which of them the repository actually has. - Diagnose why a release did not happen — hidden commit types and wrong scopes, a merge commit instead of a squash, a release job that failed after the tag was created — and repair it.
pnpx skills add TrigenSoftware/simple-release --skill simple-release-actionnpx skills add TrigenSoftware/simple-release --skill simple-release-actionconventional-commit-message
Section titled “conventional-commit-message”Simple Release derives versions and changelogs from your commit messages, so it pairs well with the conventional-commit-message skill from the conventional-changelog project. It teaches the agent to write Conventional Commit messages by release impact — choosing the type and scope that produce the right version bump, flagging breaking changes, and validating against your Commitlint config when it is available.
This matters double in monorepos: a commit bumps a package only when its scope matches the package name, and the skill derives scopes from your workspace instead of guessing.
pnpx skills add conventional-changelog/conventional-changelog --skill conventional-commit-messagenpx skills add conventional-changelog/conventional-changelog --skill conventional-commit-messageSee the conventional-changelog Agent Skills page for the full details.