skills.rest
rigerc
rigercCOMMUNITY
Explore all skills by this author →
GitHub

release-please

Automates GitHub release workflows using the release-please CLI and conventional commits.

Updated Aug 23, 2026
Search Tags:#automation#GitHub#release#bootstrap#conventional-commits#release-please
One-click install
npx skills add https://github.com/rigerc/ha-apps --skill release-please
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-please
Source: https://github.com/rigerc/ha-apps/tree/main/.claude/skills/release-please
Command: npx skills add https://github.com/rigerc/ha-apps --skill release-please

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill automates the release workflow for GitHub repositories by generating release pull requests and GitHub releases from conventional commits using Google's release-please tool.

Core Features & Use Cases

  • Bootstrap and configure release workflows for your repository with release-please.
  • Create release PRs and GitHub releases from a sequence of conventional commits, supporting both single-package and monorepo projects.
  • Apply manifest-based configuration and per-package options to manage multi-language projects (node, python, rust, java, etc.).

Quick Start

Install the release-please CLI and bootstrap a config for your repo:

  • Install: npm i -g release-please
  • Bootstrap: release-please bootstrap --token=$GITHUB_TOKEN --repo-url=<owner>/<repo> --release-type=node Then create release PRs and releases:
  • Create/update release PRs: release-please release-pr --token=$GITHUB_TOKEN --repo-url=<owner>/<repo>
  • Publish after merge: release-please github-release --token=$GITHUB_TOKEN --repo-url=<owner>/<repo>

Frequently Asked Questions about release-please

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

FAQPage Schema
How do I automate GitHub releases from conventional commits?▼

Automating GitHub releases from conventional commits involves using release-please to generate release pull requests and publish GitHub releases. The CLI parses commit history to version, changelog, and tag releases automatically.

Can I manage release workflows for a monorepo with multiple languages?▼

Yes, monorepo release workflows support multiple languages like node, python, rust, and java. Manifest-based configuration applies per-package options to manage independent versioning and releases across packages in the same repository.

How do I bootstrap release-please for a new repository?▼

To bootstrap release-please, run `release-please bootstrap` with a GitHub token and repository URL to configure the release type. This sets up the initial manifest and workflow files for automated releases.

Do I need npm and a GitHub token to run release-please commands?▼

Yes, npm is required to install the release-please CLI globally, and a GitHub token is required to run bootstrap, release-pr, and github-release commands against a repository for authentication and API access.

What is the difference between release-pr and github-release commands?▼

The release-pr command creates or updates a release pull request with version bumps and changelogs, while github-release publishes the GitHub release after merging the release PR, tagging the commit and creating the release.

Related Skills

Explore More Software Engineering Skills→
Agentic-AssetsAgentic-Assets

find-skills

Query the open agent skills ecosystem to discover and install skills.

Official
Intermediate
josemartinrodriguezmortalonijosemartinrodriguezmortaloni

git-release

Draft release notes from merged pull requests and propose version bumps.

Community
Intermediate
Sir-chawakornSir-chawakorn
33

changelog-generator

Generate changelogs from Git commits in Markdown format.

Community
Intermediate
yonatangrossyonatangross
217

release-management

Automate GitHub releases with semantic versioning and the gh CLI.

Community
Advanced