skills.rest
thuantan2060
thuantan2060COMMUNITY
Explore all skills by this author →
GitHub

release-please

Automate semantic versioning and changelog generation from Conventional Commits.

Updated May 17, 2026
Search Tags:#monorepo#github-actions#ci-cd#semantic-versioning#conventional-commits#release-automation#changelog-generation
One-click install
npx skills add https://github.com/thuantan2060/facebook-sale-tracking --skill release-please-thuantan2060
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-please
Source: https://github.com/thuantan2060/facebook-sale-tracking/tree/main/.agents/skills/release-please
Command: npx skills add https://github.com/thuantan2060/facebook-sale-tracking --skill release-please-thuantan2060

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates release versioning and changelog generation by turning Conventional Commit messages into consistent semver bumps and GitHub release PRs, so you don’t have to manually manage tags, changelogs, or release workflow wiring.

Core Features & Use Cases

  • Release PR automation: Generates or updates Release PRs based on Conventional Commits, including version determination and changelog content.
  • GitHub Actions CI/CD setup: Provides secure, production-ready workflow patterns (permissions, concurrency, publish gating, and optional idempotent publishing).
  • Ecosystem-aware publishing: Supports common targets (npm, GitHub Packages, PyPI, Maven Central, Docker, crates.io, etc.) and monorepo configurations with per-package routing.
  • Commit message assistance: Helps draft release-please-compatible Conventional Commit messages, including correct BREAKING CHANGE: footers for major bumps.

Quick Start

Ask the AI to set up release-please for your repository and specify your publish target (for example, “Set up release-please for my npm package with releases on main and publish to the public npm registry.”).

Frequently Asked Questions about release-please

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

FAQPage Schema
How do I automate semantic versioning and changelog generation from Conventional Commits in GitHub Actions?▼

Automate semantic versioning and changelog generation by configuring release-please to parse Conventional Commit history and automatically create GitHub release PRs. This eliminates manual tag management and changelog writing by mapping commit message prefixes to appropriate semver bumps.

Does release automation with release-please work for monorepo package layouts?▼

Release automation with release-please fully supports monorepo configurations by providing per-package routing for version bumps and changelog updates. You can configure a release-please manifest to manage multiple independent packages within a single repository.

How do I set up a GitHub Actions release workflow to publish npm packages using Conventional Commits?▼

Set up a GitHub Actions release workflow by defining a release-please config and manifest, then using googleapis/release-please-action@v4 to automate release PR creation. Add gated and idempotent publish steps with minimal permissions to publish your npm packages securely.

What's the best way to automate releases across multiple ecosystems like Python, Java, Go, Rust, and Docker?▼

Automate releases across multiple ecosystems by configuring release-please with ecosystem-aware publishing targets. The tool supports common registries including PyPI, Maven Central, crates.io, and Docker, generating release PRs that trigger your configured CI/CD publish steps.

How do I draft Conventional Commit messages that trigger major version bumps with release-please?▼

Draft Conventional Commit messages for major version bumps by including a `BREAKING CHANGE:` footer in your commit body. release-please parses these specific footers alongside commit prefixes like `feat:` and `fix:` to determine the correct semantic version increment.

Do I need to manually manage release tags and changelogs if I use Conventional Commits for release automation?▼

Manual tag and changelog management is unnecessary when using release-please for Conventional Commits automation. The tool automatically determines semantic versions, generates changelog content, and creates GitHub release PRs directly from your commit history.

Related Skills

Explore More Software Engineering Skills→
duongdevduongdev
9

commit-assistant

Generate conventional commit messages from git changes and link them to Linear issues.

Community
Intermediate
drvossdrvoss
42

release

Automates version tagging, changelog generation, GitHub Releases, and artifact publishing to registries.

Community
Advanced
somachaksomachak

hardening-ci-pipelines

Harden CI pipelines with secrets management, deterministic builds, and gated testing.

Community
Advanced
sgcarstrendssgcarstrends
21

release-management

Automate software release workflows with semantic-release and conventional commits.

Official
Advanced