home / skills / ehtbanton / claudeskillsrepo / semantic-release-config

semantic-release-config skill

safe

This skill generates a complete semantic-release configuration for automated versioning and publishing across npm or other platforms.

npx playbooks add skill ehtbanton/claudeskillsrepo --skill semantic-release-config

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

809 B

---
name: semantic-release-config
description: Generate semantic-release configuration for automated versioning and publishing. Triggers on "create semantic release config", "generate semantic-release configuration", "auto release setup", "release automation".
---

# Semantic Release Config Generator

Generate semantic-release configuration for fully automated versioning and publishing.

## Output Requirements

**File Output:** `.releaserc.json` or `release.config.js`
**Format:** Valid semantic-release configuration
**Standards:** semantic-release 22.x

## When Invoked

Immediately generate a complete semantic-release configuration.

## Example Invocations

**Prompt:** "Create semantic release config for npm package"
**Output:** Complete `.releaserc.json` with npm publish and changelog generation.

Overview

This skill generates a complete semantic-release configuration to automate versioning, changelog creation, and publishing. It outputs ready-to-use .releaserc.json or release.config.js formatted for semantic-release 22.x. The generated config targets TypeScript/Node projects by default and can be customized for npm, GitHub releases, or custom publish steps.

How this skill works

On trigger, the skill constructs a valid semantic-release configuration including plugins for commit-analyzer, release-notes-generator, changelog, and a publish step (npm or custom). It fills sensible defaults for conventional commits and TypeScript projects and can produce either JSON or JS config files. The result is a copy-paste-ready file that integrates with CI to enable fully automated releases.

When to use it

You want automated semantic versioning and changelog generation for an npm package.
Setting up CI to publish packages on tag/merge without manual version bumps.
Migrating a project to Conventional Commits and automated releases.
Creating a reproducible release pipeline for monorepos or single packages.
Need a starter semantic-release config for TypeScript projects.

Best practices

Use Conventional Commits style for consistent semantic-release behavior.
Run semantic-release in CI with a repository token (GH_TOKEN or NPM_TOKEN) configured as secrets.
Choose .releaserc.json for simplicity or release.config.js for dynamic logic and environment checks.
Validate generated config locally by running semantic-release in dry-run mode before enabling in CI.
Keep publish plugins minimal and add only the necessary credentials and registry settings.

Example use cases

Create .releaserc.json that publishes to npm, updates CHANGELOG.md, and creates GitHub releases.
Generate release.config.js that skips publishing for pre-release branches and runs a custom script post-release.
Provide a monorepo config that triggers per-package releases using conventional commits.
Produce a config that uses a private npm registry and includes asset uploads to GitHub releases.

FAQ

Which output format should I choose?

Use .releaserc.json for static configs and release.config.js when you need conditional logic or environment-sensitive publishing.

Does this work with semantic-release 22.x?

Yes. Generated configs are compatible with semantic-release 22.x and include recommended core plugins.