Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
日本語の概要は準備中です。原文の説明を表示しています。
davila7/claude-with-skills132026年5月15日 更新
無料GitHub で公開
release
Run the complete release workflow: changelog entry, version bump, git tag, and GitHub release. Invokes changelog-entry, tag-version, and publish in sequence. Use when releasing a new version of the project.
含まれるファイル（1）
- SKILL.md2.0 KB
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Run the complete release workflow for $ARGUMENTS (e.g., 1.2.0, patch, minor, major).
If $ARGUMENTS is empty, stop and tell the user: "Provide a version or bump type — for example: /release-plugin:release patch or /release-plugin:release 1.2.0."
Pre-flight
Check the current state before doing anything:
!git status --short 2>&1
!git describe --tags --abbrev=0 2>/dev/null && echo "latest tag found" || echo "no tags yet"
If the working tree is dirty (uncommitted changes shown above), stop and tell the user to commit or stash their changes before running the release workflow. A release must start from a clean state.
Steps
-
Run
/release-plugin:changelog-entryto generate the changelog entry for all commits since the last tag.Review the output carefully. Ask the user: "Does this changelog entry look accurate? Type 'yes' to continue or 'edit' to open CHANGELOG.md first."
If the user says 'edit', open CHANGELOG.md and wait for them to confirm they are done editing before continuing.
-
Run
/release-plugin:tag-version $ARGUMENTSto bump the version in package.json and create the annotated git tag.Confirm the tag was created by showing the output of
git describe --tags --abbrev=0. -
Run
/release-plugin:publishto push the tag to origin and create the GitHub release. -
Report the release URL returned by
/release-plugin:publish. Tell the user the release is complete.
If any step fails, stop immediately and report which step failed and what the error was. Do not attempt to continue after a failure.
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.
日本語の概要は準備中です。原文の説明を表示しています。
davila7/claude-with-skills132026年5月15日 更新
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
日本語の概要は準備中です。原文の説明を表示しています。
davila7/claude-with-skills132026年5月15日 更新
Create a git branch named after a GitHub issue.
日本語の概要は準備中です。原文の説明を表示しています。
davila7/claude-with-skills132026年5月15日 更新
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
日本語の概要は準備中です。原文の説明を表示しています。
davila7/claude-with-skills132026年5月15日 更新
Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.
日本語の概要は準備中です。原文の説明を表示しています。
davila7/claude-with-skills132026年5月15日 更新