メニュー
Cut a new release: tag the appropriate commit, generate the changelog, and produce build artifacts. Use when: releasing a new version, tagging a release, publishing NuGet packages, preparing release artifacts.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Add, remove, or apply Entity Framework Core migrations against a project under src/. Use when: creating a new migration, reverting the last migration, generating a migration bundle, applying migrations to a database.
Create a new Architectural Decision Record (ADR) capturing a justified design choice that addresses an architecturally significant functional or non-functional requirement. Use when: creating a new ADR, documenting an architectural choice, recording a design decision, superseding a previous decision, capturing rationale for a framework/library/pattern selection.
Build, test, publish, or pack .NET projects using the multi-stage Docker pipeline. Use when: building Docker images, running containerized tests, creating migration bundles, publishing to containers, or troubleshooting Dockerfile stages.
Scaffold a new reusable .NET library with correct naming, multi-targeting, and structure. Use when: creating a new library project, adding a reusable package, setting up a shared library under src/.
Scaffold a new ASP.NET web project (API or worker service) with correct structure, launch settings, and Docker integration. Use when: creating a new web API, adding an ASP.NET project, setting up a new web service under src/.
| name | new-release |
| description | Cut a new release: tag the appropriate commit, generate the changelog, and produce build artifacts. Use when: releasing a new version, tagging a release, publishing NuGet packages, preparing release artifacts. |
| argument-hint | Branch or commit to release from (default: current main) and the kind of release (stable, prerelease, hotfix) |
Versioning is GitVersion-driven (GitVersion.yml). Do not hand-pick versions — let GitVersion compute them from branch and tag history.
| Branch | Label | Resulting version |
|---|---|---|
main | — | MAJOR.MINOR.PATCH (stable) |
develop / dev / development | beta | MAJOR.MINOR.PATCH-beta.N |
release/*, hotfix/*, feature/* | branch name | …-<branch>.N |
v (regex [vV]? also accepts V or none).src/, Directory.Packages.props, or GitVersion.yml increment the version.git fetch --all --tags && git status — confirm clean.dotnet build -getProperty:Version — verify the value matches expectations.dotnet pack -c Release (or use the docker-build pack target). Artifacts land in artifacts/nuget/.git tag -a v<version> -m "Release v<version>" && git push origin v<version>.For hotfixes: branch from the latest stable tag (git switch -c hotfix/<name> v<latest-stable>), follow the procedure, then back-merge into main and develop.
PATCH — ship a fix forward.GitVersion.yml to force a version. Address the underlying cause (missing tag, branch base, path filter, commit messages).