release-setup

Generate release-please configuration, workflow, and baseline tags for Git repositories.

Updated May 8, 2026
One-click install
npx skills add https://github.com/freire19/Mythos --skill release-setup-freire19
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-setup
Source: https://github.com/freire19/Mythos/tree/main/skills/release-setup
Command: npx skills add https://github.com/freire19/Mythos --skill release-setup-freire19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of setting up automated changelogs, tags, and GitHub release PRs when a project still lacks release automation and consistent versioning.

Core Features & Use Cases

  • Repo structure detection (single vs monorepo): Scans for common manifest files (e.g., package.json, pom.xml, pyproject.toml, Cargo.toml, go.mod) and classifies the repo to choose unified vs per-package versioning.
  • release-please configuration generation: Produces a ready-to-commit GitHub Actions workflow plus release-please config and manifest tailored to the detected structure.
  • Baseline version + conventional commits alignment: Sets baseline tags/versions and warns the user when commit history doesn’t follow conventional commit patterns.
  • Optional operational choices: Supports prompts for auto-merge behavior and whether to push at the end, minimizing manual setup work.

Quick Start

Configure automated release versioning by asking the AI to run the release setup when you mention release setup, setup de versao, configurar versionamento, release-please, changelog automatico, or versionamento automatico.

Frequently Asked Questions about release-setup

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

FAQPage Schema
How do I automate GitHub releases with release-please for a monorepo?

Automated release versioning for a monorepo uses release-please to detect package manifests across Node, Maven, Python, Rust, and Go, then generates a per-package configuration and GitHub Actions workflow to handle changelogs and tags.

What's the best way to set up automated changelog generation from conventional commits?

Setting up automated changelog generation from conventional commits requires a release-please configuration and GitHub Actions workflow, which scans commit history to produce release PRs and update version files automatically.

Does release-please work with Python and Rust projects?

Yes, release-please works with Python and Rust projects by detecting package manifests like pyproject.toml and Cargo.toml, allowing you to configure automated versioning for single-package repositories or monorepos.

How do I configure baseline tags when adding release-please to an existing repository?

Configuring baseline tags when adding release-please involves scanning existing commit history and manifest files to set initial versions, then generating a release-please manifest file with user-confirmed tagging behavior.

Why does release-please require conventional commits?

Release-please requires conventional commits because it parses structured commit messages like feat and fix to determine semantic version bumps, automatically generating changelogs and release PRs based on those specific patterns.