Stats
Actions
Tags
From configure-plugin
Checks and configures release-please GitHub Actions workflows for project standards including latest version, tokens, triggers, and project-type detection for Node/Python/Go/Rust.
How this skill is triggered — by the user, by Claude, or both
Slash command
/configure-plugin:configure-release-pleaseThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Check and configure release-please against project standards.
Check and configure release-please against project standards.
| Use this skill when... | Use another approach when... |
|---|---|
| Setting up release-please for a new project from scratch | Manually editing CHANGELOG.md or version fields — use conventional commits instead |
| Auditing existing release-please configuration for compliance | Creating a one-off release — use gh release create directly |
| Upgrading release-please-action to the latest version | Debugging a failed release PR — check GitHub Actions logs directly |
| Ensuring workflow uses correct token (MY_RELEASE_PLEASE_TOKEN) | Managing npm/PyPI publishing — configure separate publish workflows |
| Adding a new package to a monorepo release-please configuration | Writing conventional commit messages — use /git:commit skill |
find .github/workflows -maxdepth 1 -name 'release-please*'find . -maxdepth 1 -name \'release-please-config.json\'find . -maxdepth 1 -name \'.release-please-manifest.json\'find . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' -o -name 'go.mod' \)find . -maxdepth 1 -type d -name \'.github/workflows\'Skills referenced: release-please-standards, release-please-protection
Parse from command arguments:
--check-only: Report status without offering fixes--fix: Apply all fixes automaticallyExecute this release-please configuration check:
Run this command to get the current release-please-action version dynamically:
curl -s https://api.github.com/repos/googleapis/release-please-action/releases/latest | jq -r '.tag_name'
References:
Determine appropriate release-type from detected package files:
package.json (default for frontend/backend apps)pyproject.toml without package.jsonWorkflow file checks:
googleapis/release-please-action@v4MY_RELEASE_PLEASE_TOKEN secret (not GITHUB_TOKEN)main branchcontents: write, pull-requests: writeConfig file checks:
feat and fixnode-workspace for Node projects)Manifest file checks:
Print a formatted compliance report showing file status and configuration check results. If --check-only is set, stop here.
For the report format, see REFERENCE.md.
0.0.0For standard templates, see REFERENCE.md.
Update .project-standards.yaml:
components:
release-please: "2025.1"
| Context | Command |
|---|---|
| Quick compliance check | /configure:release-please --check-only |
| Auto-fix all issues | /configure:release-please --fix |
| Check latest action version | curl -s https://api.github.com/repos/googleapis/release-please-action/releases/latest | jq -r '.tag_name' |
| Verify config JSON | jq . release-please-config.json |
| Verify manifest JSON | jq . .release-please-manifest.json |
| Check workflow exists | find .github/workflows -name 'release-please*' |
MY_RELEASE_PLEASE_TOKEN secret in repository settingsconventional-pre-commit hook for commit validation/configure:pre-commit - Ensure conventional commits hook/configure:all - Run all compliance checksrelease-please-protection skill - Protected file rulesnpx claudepluginhub laurigates/claude-plugins --plugin configure-pluginProvides standard release-please configurations for GitHub Actions workflows to automate semantic versioning, changelog generation, and releases for Node.js, Python, Helm, and multi-package repos.
Configures Google's release-please for automated versioning, changelog generation, and publishing via GitHub Actions using Conventional Commits.
Configures Google's release-please for automated semantic versioning, changelog generation, and GitHub releases in single-package and monorepo repositories.