Skip to content

AterDev/Perigon.CLI / .agents/skills/release

release

Verified

Prepare and publish Perigon.CLI patch releases, including versioning, release notes, bilingual docs, validation, and the nuget-branch CI handoff.

FileKindSize
SKILL.mdskill md2.7 KB
---
name: release
description: Prepare and publish Perigon.CLI patch releases, including versioning, release notes, bilingual docs, validation, and the nuget-branch CI handoff.
---

# Perigon.CLI Release Workflow

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.

## Before editing

- Inspect `git status` in both `Perigon.CLI` and `Perigon.docs` repositories.
- Preserve unrelated user changes. Stage only files belonging to the release.
- Confirm the exact current version from `src/Apps/CommandLine/CommandLine.csproj`.

## Release contents

- Unless the user specifies a version, increment only the patch component of `<Version>` in `src/Apps/CommandLine/CommandLine.csproj`.
- Keep `src/Apps/Dashboard/Dashboard.csproj` on the same version.
- Update `<PackageReleaseNotes>` with only the changes being released.
- Update the matching Chinese and English pages under `Perigon.docs/Content/docs/Perigon`, normally the command-line page and the version update notes. Keep their structure and meaning aligned.
- Add or update reusable release guidance in this skill and `Contribution.md` when the workflow changes.

## Validation

Run the focused tests for the changed feature, then the full test project:

```powershell
dotnet test tests/StudioMod.Tests/CoreMod.Tests.csproj --configuration Release --verbosity minimal
```

The CI-equivalent package/studio build is:

```powershell
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.

## Branch handoff

1. Commit the Perigon.CLI release changes on the current development branch with a conventional emoji-prefixed message such as `πŸš€ release: prepare Perigon.CLI 10.1.12`.
2. Push that branch if it is the requested source branch.
3. Fetch `origin/nuget`, verify it has no unexpected divergence, merge the release commit into a local `nuget` branch, and push `nuget` without force-pushing.
4. add git tag `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.

## Docs repository

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.
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product β€” it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product β€” not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial β€” a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK β€” model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER β€” read BEFORE opening the target file; don't skip because it "looks like a one-liner" β€” whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) β€” never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named β€” don't Read the file).Stars: 197kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 197kUpdated Claude CodeCodexVerifiedInstall