Automated summary
Automates the release process: secret checking (gitleaks), CHANGELOG generation, version bump, commit, tag, and push.
Strengths
- Integrates gitleaks security scanning before each release
- Auto-generates a structured CHANGELOG from commit history
- Updates three version files simultaneously (package.json, Cargo.toml, tauri.conf.json)
Limitations
- Requires gitleaks to be installed in the environment
- Commit categorization into changelog sections may be inaccurate
- Does not handle merge conflicts or push errors
When preparing a new version of a Tauri/Node.js project and need a standardized, secure release workflow.
For releases requiring complex manual validation or custom build steps not covered by the automation.
Security analysis
CautionThe skill automates a release process involving git push, npm, and gitleaks. All actions are standard for a release workflow, and it includes a secret scan step and user confirmation to mitigate risks. No destructive or malicious commands.
- •Executes git push to remote repository, which could propagate changes unintentionally if the user is not careful. However, user confirmation is required.
- •Uses npm install --package-lock-only, which is generally safe but modifies lockfile.
- •Runs gitleaks, a third-party tool, which is fine for its purpose.
Examples
v1.4.0 をリリースしたいリリースしたいname: release description: 機密情報チェック→CHANGELOG生成→バージョンバンプ→コミット→タグ→プッシュのリリース作業を実行。「リリースしたい」「vX.Y.Z をリリース」と言った時に使用 argument-hint: <version>
Leaner Waigaya リリース手順
引数として新バージョン（例: 1.4.0）を受け取り、以下の手順でリリース作業を行う。
手順
1. 準備確認
- 引数の
<version>からvプレフィックスを除去して正規化する（例:v1.4.0→1.4.0） package.jsonの現在バージョンを読んで直前タグ（例:v1.3.0）を確認する- ユーザーに確認する：「現在 X.Y.Z → v{version} にリリースします。よろしいですか？」
git statusでコミットされていない変更がないか確認する（あれば警告）
2. 機密情報チェック（gitleaks）
直前タグからHEADまでの差分を gitleaks でスキャンする：
gitleaks detect --log-opts="-p v{prevVersion}..HEAD"
- 検出あり: リリースを中断し、該当箇所をユーザーに報告する
- 検出なし: 「機密情報は検出されませんでした」と報告して次へ進む
3. CHANGELOG.md 生成
git log v{prevVersion}..HEAD --oneline でコミット一覧を取得し、内容を読んで以下の形式で CHANGELOG.md の先頭に追記する（既存の CHANGELOG.md がなければ新規作成）：
## [X.Y.Z] - YYYY-MM-DD
### Added
- 新機能の説明
### Fixed
- バグ修正の説明
### Changed
- 変更の説明
- バージョンバンプ用コミットメッセージ（例: "v1.3.0 リリース"）はChangelog から除外する
- コミットメッセージから内容を推測して適切なカテゴリに分類する
4. バージョンバンプ（3ファイル同時更新）
以下の3ファイルのバージョン文字列を更新する：
| ファイル | 更新箇所 |
|----------|----------|
| package.json | "version": "..." |
| src-tauri/Cargo.toml | version = "..." |
| src-tauri/tauri.conf.json | "version": "..." |
5. package-lock.json 更新
npm install --package-lock-only
6. コミット
git add CHANGELOG.md package.json package-lock.json src-tauri/Cargo.toml src-tauri/tauri.conf.json
git commit -m "v{version} リリース"
7. タグ作成 & プッシュ
git tag v{version}
git push origin main
git push origin v{version}
8. 完了報告
リリース完了後、以下を報告する：
- タグ
v{version}を作成してプッシュした旨 - GitHub Actions が自動ビルド・リリースを実行している旨
- GitHub のリリースページ URL（リポジトリ:
leaner-co-jp/leaner-waigaya）
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/release-automation-workflow-mmbizj7o/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/release-automation-workflow-mmbizj7o' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/release-automation-workflow-mmbizj7o/download' --output '.skill-downloads/release-automation-workflow-mmbizj7o/SKILL.md.part' && mv '.skill-downloads/release-automation-workflow-mmbizj7o/SKILL.md.part' '.skill-downloads/release-automation-workflow-mmbizj7o/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/release-automation-workflow-mmbizj7o/SKILL.md' && test -s '.skill-downloads/release-automation-workflow-mmbizj7o/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/release' && cp -R '.skill-downloads/release-automation-workflow-mmbizj7o' '.claude/skills/release'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/release-automation-workflow-mmbizj7o'openskills read 'release-automation-workflow-mmbizj7o'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/release-automation-workflow-mmbizj7o/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.