Prepare and publish Perigon.CLI patch releases, including versioning, release notes, bilingual docs, validation, and the nuget-branch CI handoff.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this skill when releasing Perigon.CLI or when the user asks to package and publish a version. The NuGet publishing workflow runs automatically when origin/nuget receives a push.
git status in both Perigon.CLI and Perigon.docs repositories.src/Apps/CommandLine/CommandLine.csproj.<Version> in src/Apps/CommandLine/CommandLine.csproj.src/Apps/Dashboard/Dashboard.csproj on the same version.<PackageReleaseNotes> with only the changes being released.Perigon.docs/Content/docs/Perigon, normally the command-line page and the version update notes. Keep their structure and meaning aligned.Contribution.md when the workflow changes.Run the focused tests for the changed feature, then the full test project:
dotnet test tests/StudioMod.Tests/CoreMod.Tests.csproj --configuration Release --verbosity minimal
The CI-equivalent package/studio build is:
pwsh ./scripts/PublishToLocal.ps1 -withStudio:$true
PublishToLocal.ps1 reads the tracked src/Apps/CommandLine/ShareDlls.txt when packaging Studio and removes the listed duplicate DLLs. If project dependencies change, run scripts/CheckSharedDlls.ps1 to refresh the list and commit the updated file.
Run it only after tests pass; it creates local publish/package artifacts and may install the package locally.
🚀 release: prepare Perigon.CLI 10.1.12.origin/nuget, verify it has no unexpected divergence, merge the release commit into a local nuget branch, and push nuget without force-pushing.v<version> to the release commit and push the tag.If the nuget branch has unrelated commits or conflicts, stop before merging and report the exact divergence. Do not reset, discard, or force-push user work.
Commit and push only the release-related files in Perigon.docs; leave any pre-existing uncommitted documentation changes untouched. Verify both zh-CN and en-US pages before handing off.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use for Blazor Server development with Fluent UI Blazor, Razor components, layouts, pages, scoped UI services, culture switching, localization, forms, loading/empty/error states, and Studio-style dashboard workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Use for .NET command-line tool development with Spectre.Console/Spectre.Console.Cli, Microsoft.Extensions.Hosting, dependency injection, localized help text, command settings, aliases, examples, terminal output, exit codes, and stdio-safe command paths.
日本語の概要は準備中です。原文の説明を表示しています。
Use for .NET code generation work with Roslyn, Microsoft.OpenApi, Razor templates, DTO/manager/controller generation, REST API generation, C# HttpClient generation, Angular/Axios TypeScript request clients, generated formatting, and deterministic output.
日本語の概要は準備中です。原文の説明を表示しています。
Use for Perigon documentation work across this workspace, especially Perigon.docs/Content/docs/Perigon bilingual and versioned docs, syncing zh-CN and en-US content, updating docs from Perigon.CLI, Perigon.template, and Perigon.Modules changes, and deciding whether to revise existing pages or add new documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Use for .NET application development involving services, managers, dependency injection, Microsoft.Extensions.Hosting, dependency direction, MiniDb persistence, DTOs, Mapster mapping, shared entities/helpers, MCP tools, module workflows, solution analysis, cancellation, logging, and logic shared by CLI and Blazor.
日本語の概要は準備中です。原文の説明を表示しています。
Use for .NET test design and validation with xUnit v3, Moq, focused regression tests, command tests, service/manager tests, code generation tests, Roslyn helper tests, MiniDb isolation, HTTP stubs, temp directories, and deciding whether to run targeted tests or builds.
日本語の概要は準備中です。原文の説明を表示しています。