メニュー
Creates a new Revela release by updating CHANGELOG.md, committing changes, and creating a git tag. Use when the user asks to create a release, prepare a release, bump the version, or tag a new version.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Builds a local Revela release for testing using scripts/build-release.ps1. Mirrors the GitHub release pipeline output — produces Standalone or Full variants. Use when the user wants to build a release locally, test packaging, create a self-contained executable, verify what end users would download, or validate the release before publishing.
Builds a sample project (revela-website, showcase, onedrive) using the local CLI. Use when the user wants to build a sample, generate a site, test output, preview the website, or regenerate pages/images.
Reviews C# code against Revela project conventions, .editorconfig rules, and .NET 10 best practices. Covers naming, patterns, async, logging, DI, configuration, commands, testing, and code style. Use when reviewing code, suggesting improvements, or checking for convention violations in the Revela codebase.
Creates git commits with comprehensive, Conventional Commits-formatted messages. Use when the user asks to commit, stage changes, save progress, or create a commit message. Ensures consistent, descriptive commit messages following project conventions.
Runs the end-to-end release pipeline test using scripts/test-release.ps1. Tests build, pack, plugin install, generate all, compress, clean, idempotency, and dotnet tool install. Use when the user wants to test a release, verify the pipeline, check packaging, or validate before publishing.
| name | create-release |
| description | Creates a new Revela release by updating CHANGELOG.md, committing changes, and creating a git tag. Use when the user asks to create a release, prepare a release, bump the version, or tag a new version. |
| argument-hint | [version e.g. 0.5.0 or 0.5.0-beta.1] |
Prepare and create a new release for Revela. Follow all steps in order. Do NOT commit or push automatically — present changes and let the user decide.
Before starting, verify:
dotnet test)git status)[Unreleased] section in CHANGELOG.md has contentAsk the user for the version number if not provided. Follow Semantic Versioning:
0.0.1-beta.15, 0.0.1-rc.11.0.0, 1.0.1, 1.1.0Check the latest version in CHANGELOG.md. The new version must be higher than the previous one.
The changelog follows Keep a Changelog format.
Replace ## [Unreleased] content with the new version and today's date:
## [Unreleased]
## [X.Y.Z-suffix] - YYYY-MM-DD
Add comparison link at the bottom of the file:
[Unreleased]: https://github.com/spectara/revela/compare/vX.Y.Z-suffix...HEAD
[X.Y.Z-suffix]: https://github.com/spectara/revela/compare/vPREVIOUS...vX.Y.Z-suffix
Update the existing [Unreleased] link to point to the new tag.
Verify the [Unreleased] section is now empty (ready for next development cycle).
Show the user what was changed and suggest next steps:
git add CHANGELOG.md
git commit -m "Release vX.Y.Z-suffix"
git tag vX.Y.Z-suffix
git push origin main --tags
Do NOT execute these commands automatically. Let the user review and decide.
Note: Directory.Build.props does NOT need updating — the release workflow passes the version from the git tag via -p:Version= and -p:PackageVersion= build parameters.
The release pipeline (.github/workflows/release.yml) handles everything after the tag push:
nuget-org environment approval)Additional workflows triggered after release:
deploy-website.yml — Deploy revela.websiteBefore presenting to the user, verify:
[Unreleased] section is empty