Configure automated versioning with release-please. Set up semantic versioning, changelog generation, and monorepo support using GitHub App token authentication.
Sets up release-please for automated versioning and changelog generation. Configures semantic versioning, monorepo support, and GitHub App authentication when setting up release pipelines.
/plugin marketplace add adaptive-enforcement-lab/claude-skills/plugin install build@ael-skillsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
examples.mdscripts/example-1.jsonscripts/example-2.jsonscripts/example-3.jsonRelease-please reads your commit history and:
Release-please automates version management based on conventional commits. It creates release PRs with updated changelogs, version bumps, and Git tags.
Schema Validation
Always include the
$schemaproperty in your config file. It catches invalid options immediately and saves debugging time.
Release-please reads your commit history and:
The main configuration file defines packages and their versioning behavior:
See examples.md for detailed code examples.
Tracks current versions for each package:
{
"charts/my-app": "1.0.0",
"packages/backend": "1.0.0",
"packages/frontend": "1.0.0"
}
| Option | Description | Example |
|---|---|---|
include-v-in-tag | Prefix tags with v | true = v1.0.0, false = 1.0.0 |
tag-separator | Separator between component and version | - = backend-1.0.0 |
separate-pull-requests | Create one PR per component | Recommended for monorepos |
changelog-sections | How to group commits in changelogs | See example above |
| Option | Description | Values |
|---|---|---|
release-type | Package ecosystem | node, helm, simple, python, go, etc. |
component | Component name for tagging | Any string |
include-component-in-tag | Include component in tag | true = backend-1.0.0 |
package-name | Package name (for node, etc.) | Matches package.json name |
Always validate configuration against the official schema:
{
"$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json"
}
This catches invalid options immediately. Options like release-name don't exist. The schema prevents wasted debugging time.
Release-please reads your commit history and:
The main configuration file defines packages and their versioning behavior:
See examples.md for detailed code examples.
Tracks current versions for each package:
{
"charts/my-app": "1.0.0",
"packages/backend": "1.0.0",
"packages/frontend": "1.0.0"
}
| Option | Description | Example |
|---|---|---|
include-v-in-tag | Prefix tags with v | true = v1.0.0, false = 1.0.0 |
tag-separator | Separator between component and version | - = backend-1.0.0 |
separate-pull-requests | Create one PR per component | Recommended for monorepos |
changelog-sections | How to group commits in changelogs | See example above |
| Option | Description | Values |
|---|---|---|
release-type | Package ecosystem | node, helm, simple, python, go, etc. |
component | Component name for tagging | Any string |
include-component-in-tag | Include component in tag | true = backend-1.0.0 |
package-name | Package name (for node, etc.) | Matches package.json name |
Always validate configuration against the official schema:
{
"$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json"
}
This catches invalid options immediately. Options like release-name don't exist. The schema prevents wasted debugging time.
See examples.md for code examples.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.