菜单
Execute the full release workflow: bump version, update changelog, run dotnet format and dotnet test quality gates, prepare release notes, commit and push to main, wait for CI green, then create and push the annotated tag. WHEN: shipping a new release, bumping version in the repo, creating a git tag, or running pre-release quality gates.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | release-process |
| description | Execute the full release workflow: bump version, update changelog, run dotnet format and dotnet test quality gates, prepare release notes, commit and push to main, wait for CI green, then create and push the annotated tag. WHEN: shipping a new release, bumping version in the repo, creating a git tag, or running pre-release quality gates. |
| domain | release-management |
| confidence | high |
| source | manual |
Use this skill when preparing and shipping a release from main in this repository. It standardizes the release order and enforces a hard CI gate before tags are created.
git checkout maingit fetch origingit pull --ff-only origin mainCHANGELOG.md with date, version, and notable changes.dotnet format --verify-no-changes — verify formatting; fix any issues before proceeding.dotnet test — all tests must pass; do NOT proceed if any test fails.chore(release): vX.Y.Z.git push origin mainmain is fully green.git tag -a vX.Y.Z -m "vX.Y.Z"git push origin vX.Y.Zgit push --tags.git checkout main
git fetch origin
git pull --ff-only origin main
# edit version + CHANGELOG + release notes (Leela)
dotnet format --verify-no-changes
dotnet test
git add <version-files> CHANGELOG.md <release-notes-files>
git commit -m "chore(release): vX.Y.Z"
git push origin main
# wait for CI green
git tag -a vX.Y.Z -m "vX.Y.Z"
git push origin vX.Y.Z
maindotnet test first{what this skill teaches agents}
Add boolean configuration flags to the update-config CLI command using TryParseRequiredBoolean() for argument parsing and GetOrCreateObject() for JSON section navigation, following the three-step flow and nesting conventions established across PRs #85, #86, and #92. WHEN: adding a new --flag to update-config, nesting a config value under a JSON section, or writing unit tests for CLI config flag parsing.
Resolve configuration file paths in CLI commands using the same shared pipeline as the doctor/diagnostics so all commands target the same effective config file. WHEN: adding a new CLI command that reads or writes config, debugging a command that mutates a different config file than doctor reports, or implementing config-aware CLI behavior in a multi-location config environment.
Implement discovery-source attribution tracking for MCP tool enumeration by creating a dedicated tracker interface with first-writer-wins semantics, recording at discovery call sites (not in the doctor/reporter), and wiring both in-process and OOP paths to agree on provenance. WHEN: the doctor or a reporting surface infers tool source heuristically, adding source attribution to a new discovery path, or aligning in-process and OOP discovery provenance.
Implement OAuth 2.1 + Entra ID authentication for an MCP server using a lightweight AS metadata proxy — handling RFC 9728 protected resource metadata, RFC 8414 AS metadata, and a /register endpoint that eliminates client_id prompts for all MCP clients. WHEN: adding OAuth to an MCP server, MCP clients ask users to paste a client_id, authorization redirects go to the wrong endpoint, or debugging Entra DCR limitations.
Publish .NET NuGet packages to GitHub Packages using GitHub PAT authentication — covering gh auth token retrieval, write:packages scope verification, dotnet pack/push workflow, and owner resolution from git remote. WHEN: publishing a NuGet package to GitHub Packages, debugging 401 on dotnet nuget push, adding a GitHub Packages NuGet source, or resolving write:packages scope errors.