How do I install the Payload Plugin Release skill?

Run npx get-skill add tomevault-io/payload-plugin-release in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Payload Plugin Release safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Payload Plugin Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Payload Plugin Release free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Payload Plugin Release?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Payload Plugin Release by tomevault-io

Name: Payload Plugin Release
Author: tomevault-io

File contents

Patch (bug fixes) - e.g., 0.25.11 → 0.25.12
Minor (new features, backward compatible) - e.g., 0.25.11 → 0.26.0
Major (breaking changes) - e.g., 0.25.11 → 1.0.0

Also provide: What changes are being released? (for changelog)

## [NEW_VERSION] - YYYY-MM-DD

### Fixed/Added/Changed
- Description of changes

Categories to use:

Added - new features
Changed - changes in existing functionality
Fixed - bug fixes
Removed - removed features
Security - security fixes

GitHub Actions will automatically:

Detect the new version
Run tests and type checking
Build the project
Create the git tag
Publish to npm
Create a GitHub release

Source: aniketpanjwani/payload-plugin-email-newsletter — distributed by TomeVault.

---name: payload-plugin-releasedescription: Automates the release workflow for the Payload Newsletter Plugin. Use when releasing a new version, bumping the version, or publishing to npm.---<objective>Execute the automated release workflow for the Payload Newsletter Plugin, ensuring proper versioning, changelog updates, and triggering GitHub Actions for npm publishing.</objective><essential_principles>- NEVER create git tags manually - GitHub Actions handles tag creation- ALWAYS check the current date before updating changelog- ALWAYS run typecheck before committing release changes- Version bumps follow semantic versioning (major.minor.patch)</essential_principles><intake>What type of release?1. **Patch** (bug fixes) - e.g., 0.25.11 → 0.25.122. **Minor** (new features, backward compatible) - e.g., 0.25.11 → 0.26.03. **Major** (breaking changes) - e.g., 0.25.11 → 1.0.0Also provide: What changes are being released? (for changelog)</intake><process><step name="verify">Run typecheck to ensure no TypeScript errors:```bashbun typecheck```If errors exist, fix them before proceeding.</step><step name="get-current-version">Check current version:```bashgrep '"version"' package.json | head -1```</step><step name="get-date">Get current date for changelog:```bashdate +"%Y-%m-%d"```</step><step name="bump-version">Update version in package.json based on release type:- Patch: increment last number (0.25.11 → 0.25.12)- Minor: increment middle, reset last (0.25.11 → 0.26.0)- Major: increment first, reset others (0.25.11 → 1.0.0)</step><step name="update-changelog">Add entry at TOP of CHANGELOG.md:```markdown## [NEW_VERSION] - YYYY-MM-DD### Fixed/Added/Changed- Description of changes```Categories to use:- **Added** - new features- **Changed** - changes in existing functionality- **Fixed** - bug fixes- **Removed** - removed features- **Security** - security fixes</step><step name="commit-and-push">```bashgit add package.json CHANGELOG.mdgit commit -m "chore: release vX.Y.Z"git push origin main```GitHub Actions will automatically:1. Detect the new version2. Run tests and type checking3. Build the project4. Create the git tag5. Publish to npm6. Create a GitHub release</step><step name="monitor">Direct user to monitor the release:https://github.com/aniketpanjwani/payload-plugin-email-newsletter/actions</step></process><success_criteria>- TypeScript passes with no errors- Version bumped correctly in package.json- CHANGELOG.md updated with correct date and version- Changes committed and pushed to main- User directed to GitHub Actions to monitor release</success_criteria>---> Source: [aniketpanjwani/payload-plugin-email-newsletter](https://github.com/aniketpanjwani/payload-plugin-email-newsletter) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Payload Plugin Release