mcpField
C
configure-release-please

configure-release-please

github.com/laurigatesCloud & DevOps5956 installsUpdated 1d ago
Repository

About configure-release-please

An agent skill that audits and configures release-please, including its workflow, configuration, and version manifest. It detects a release type from project files and offers compliance checks with optional automatic fixes.

Key features

  1. 01Audit release-please configuration
  2. 02Detect release type from project files
  3. 03Check workflow, token, and permissions
  4. 04Create or update release configuration files
  5. 05Update project standards tracking

Use cases

  1. 01Set up release-please for a new project
  2. 02Audit an existing release workflow and config
  3. 03Add a package to monorepo release configuration
  4. 04Fix outdated action versions or token settings

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/laurigates/claude-plugins --skill configure-release-please

After installing, type/configure-release-pleasein Claude Code to confirm it loaded.

Bundled filesREFERENCE.md

Details

From the project README

/configure:release-please

Check and configure release-please against project standards.

When to Use This Skill

Use this skill when...Use another approach when...
Setting up release-please for a new project from scratchManually editing CHANGELOG.md or version fields — use conventional commits instead
Auditing existing release-please configuration for complianceCreating a one-off release — use gh release create directly
Upgrading release-please-action to the latest versionDebugging 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 configurationWriting conventional commit messages — use /git:commit skill

Context

  • Workflow file: !find .github/workflows -maxdepth 1 -name 'release-please*'
  • Config file: !find . -maxdepth 1 -name \'release-please-config.json\'
  • Manifest file: !find . -maxdepth 1 -name \'.release-please-manifest.json\'
  • Package files: !find . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' -o -name 'go.mod' \)
  • Workflows dir: !find . -maxdepth 1 -type d -name \'.github/workflows\'

Skills referenced: release-please-standards, release-please-protection

Parameters

Parse from command arguments:

  • --check-only: Report status without offering fixes
  • --fix: Apply all fixes automatically

Execution

Execute this release-please configuration check:

Step 1: Fetch latest action version

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:

Step 2: Detect project type

Determine appropriate release-type from detected package files:

  • node: Has package.json (default for frontend/backend apps)
  • python: Has pyproject.toml without package.json
  • helm: Infrastructure with Helm charts
  • simple: Generic projects
Step 3: Analyze compliance

Workflow file checks:

  • Action version: googleapis/release-please-action@v4
  • Token: Uses MY_RELEASE_PLEASE_TOKEN secret (not GITHUB_TOKEN)
  • Trigger: Push to main branch
  • Permissions: contents: write, pull-requests: write

Config file checks:

  • Valid release-type for project
  • changelog-sections includes feat and fix
  • Appropriate plugins (e.g., node-workspace for Node projects)

Manifest file checks:

  • Valid JSON structure
  • Package paths match config
Step 4: Generate compliance report

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.

Step 5: Apply configuration (if --fix or user confirms)
  1. Missing workflow: Create from standard template
  2. Missing config: Create with detected release-type
  3. Missing manifest: Create with initial version 0.0.0
  4. Outdated action: Update to v4
  5. Wrong token: Update to use MY_RELEASE_PLEASE_TOKEN

For standard templates, see REFERENCE.md.

Step 6: Update standards tracking

Update .project-standards.yaml:

components:
  release-please: "2025.1"

Agentic Optimizations

ContextCommand
Quick compliance check/configure:release-please --check-only
Auto-fix all issues/configure:release-please --fix
Check latest action versioncurl -s https://api.github.com/repos/googleapis/release-please-action/releases/latest | jq -r '.tag_name'
Verify config JSONjq . release-please-config.json
Verify manifest JSONjq . .release-please-manifest.json
Check workflow existsfind .github/workflows -name 'release-please*'

Important Notes

  • Requires MY_RELEASE_PLEASE_TOKEN secret in repository settings
  • CHANGELOG.md is managed by release-please - never edit manually
  • Version fields in package.json/pyproject.toml are managed automatically
  • Works with conventional-pre-commit hook for commit validation

See Also

  • /configure:pre-commit - Ensure conventional commits hook
  • /configure:all - Run all compliance checks
  • release-please-protection skill - Protected file rules

Comments

Markdown supported