skills.rest
nikbrunner
nikbrunnerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dev-setup-release-please

Configure Release Please for repositories by detecting project type and generating GitHub Actions files.

Updated Jun 17, 2025
Search Tags:#automation#devops#github-actions#continuous-delivery#semantic-versioning#release-please#workflow-config
One-click install
npx skills add https://github.com/nikbrunner/dots --skill dev-setup-release-please
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-setup-release-please
Source: https://github.com/nikbrunner/dots/tree/main/common/.agents/skills/dev-setup-release-please
Command: npx skills add https://github.com/nikbrunner/dots --skill dev-setup-release-please

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates configuring Release Please for a repository by detecting project type and generating a release workflow, manifest, and permissions setup.

Core Features & Use Cases

  • Detects the default branch of the repository.
  • Detects project type (Node, Go, Deno, Obsidian plugin) and configures release-please accordingly.
  • Creates required GitHub Actions workflow files and enables PR permissions as needed.

Quick Start

Run the /setup-release-please <version> in your repository to initialize Release Please.

Frequently Asked Questions about dev-setup-release-please

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

FAQPage Schema
How do I automate Release Please configuration for a GitHub Actions workflow?▼

You can automate Release Please configuration by running a setup command that detects your default branch and project type, then generates the necessary GitHub Actions workflow, manifest, and permissions files automatically.

Does Release Please auto-detect project types like Node, Go, and Deno?▼

Yes, Release Please setup auto-detects project types including Node, Go, Deno, and Obsidian plugins. It uses this detection to tailor the generated release workflows and configuration files to your specific environment.

What files are required to set up semantic versioning with Release Please?▼

Setting up Release Please requires generating specific files: .github/release-please-config.json, .github/.release-please-manifest.json, and .github/workflows/release.yml, along with optional cleanup and permission adjustments.

How do I configure GitHub Actions permissions for continuous delivery with Release Please?▼

Configuring GitHub Actions permissions for Release Please is handled automatically during setup. The process creates the required workflow files and enables pull request permissions as needed to facilitate continuous delivery.

Can I use Release Please to manage semantic versioning across multiple repositories?▼

Yes, you can use this setup process across multiple repositories to auto-configure Release Please. It standardizes semantic versioning by generating consistent manifest and workflow configurations tailored to each detected project type.

Related Skills

Explore More Software Engineering Skills→
PiklarPiklar

speckit-git-feature

Create and switch git feature branches using project-defined naming conventions.

Community
Intermediate
lbrutonlbruton
8

release

Automate version bumps, changelog updates, commits, and GitHub pull requests.

Community
Advanced
JhabbigJhabbig

changelog-automation

Generate changelogs from commits and pull requests with Keep a Changelog formatting.

Community
Advanced
aroidoaroido

command-release

Automate software releases with version tags and GitHub Actions.

Official
Advanced