用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/tomevault-io/skills-registry --skill release-please-configuration命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
| Use when this capability is needed.
> Use when this capability is needed.
Review architecture and API design for the vfs-s3 project. Use when the user mentions @architect, asks to review an issue's design, discuss module boundaries, API shape, or architectural decisions for vfs-s3. Also trigger when the user wants to create an ADR (Architecture Decision Record) or evaluate a technical approach for the project. Intended for dispatch from Codex automation or Claude routines; GitHub trigger phrase: @vfs-s3-bot please prepare design doc Use when this capability is needed.
基于 SOC 职业分类
正在显示 SKILL.md
| name | release-please-configuration |
| description | >- Use when this capability is needed. |
Release-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.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.