release-please-development

Automates version bumps, changelog generation, and GitHub releases via Release Please.

23|2|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/dwmkerr/claude-toolkit --skill release-please-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-please-development
Source: https://github.com/dwmkerr/claude-toolkit/tree/main/plugins/toolkit/skills/release-please-development
Command: npx skills add https://github.com/dwmkerr/claude-toolkit --skill release-please-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates release management tasks, including version bumps, changelog generation, and GitHub release creation for projects using Release Please, reducing manual effort and ensuring consistency across teams.

Core Features & Use Cases

  • Automatic version bumps based on conventional commits
  • CHANGELOG.md generation and synchronized updates
  • GitHub release creation and tagging with per-package support
  • Per-repo configuration for monorepos and multi-project setups
  • Simple integration with GitHub Actions workflows to automate releases

Quick Start

Configure Release Please in your repository by adding .github/release-please-config.json and .github/release-please-manifest.json, then create a GitHub Actions workflow at .github/workflows/release.yaml. A minimal setup uses googleapis/release-please-action@v4 with the two config files to manage releases on pushes to main.

Frequently Asked Questions about release-please-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate semantic versioning and changelog generation for GitHub repositories?

Automate semantic versioning and changelog generation by using conventional commits to trigger automatic version bumps and CHANGELOG.md updates via GitHub Actions workflows configured with release-please.

How do I set up Release Please for a monorepo with multiple packages?

Set up Release Please for monorepos by adding .github/release-please-config.json and release-please-manifest.json, which enable per-package configurations and synchronized GitHub release tagging across multiple projects.

What configuration files are required to use the release-please-action in GitHub Actions?

Using release-please-action requires adding .github/release-please-config.json and release-please-manifest.json, alongside a .github/workflows/release.yaml file to manage releases on pushes to your main branch.

Can I manage multi-project releases and per-repo configurations using conventional commits?

Manage multi-project releases using conventional commits with per-repo configurations in monorepo setups, allowing distinct version bumps and GitHub release creation for individual packages within the same repository.

Does Release Please work without external dependencies for automating GitHub releases?

Release Please works without external dependencies, requiring only standard GitHub Actions workflows and JSON/YAML configuration files to automate versioning, changelog generation, and release tagging.