菜单
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.
用 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.
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.
| name | test-release |
| description | 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. |
| argument-hint | [--SkipTests] [--IncludeOneDrive] [--Version 0.0.0-test] |
| context | fork |
Run a full end-to-end release pipeline test locally. Validates that the entire release workflow works: build, pack, publish, install plugins, generate a site, and install as dotnet tool.
.\scripts\test-release.ps1
| Parameter | Default | Description |
|---|---|---|
-Version | 0.0.0-test | Version number for the test build |
-SkipTests | (off) | Skip unit tests for faster iteration |
-IncludeOneDrive | (off) | Also test OneDrive sync (requires network + valid share URL) |
-KeepArtifacts | (off) | Keep test artifacts after completion |
-RuntimeIdentifier | auto-detected | Target platform (win-x64, linux-x64, osx-x64, etc.) |
The script runs 13 sequential steps:
| Step | What | Validates |
|---|---|---|
| 1 | Clean & Prepare | Test directory setup |
| 2 | Restore & Build | Solution compiles in Release |
| 3 | Run Tests | All unit + integration tests pass (skippable) |
| 4 | Publish CLI | Self-contained executable works |
| 5 | Build NuGet Packages | All plugins, themes, SDK pack correctly |
| 6 | Integration Setup | Showcase sample copied to temp dir |
| 7 | Install Plugins | Plugin install from local NuGet feed |
| 7b | Verify Plugins | Plugin list, uninstall, re-install, serve --help |
| 7c | Theme List | Built-in theme + online search |
| 7d | OneDrive Sync | Optional, requires -IncludeOneDrive |
| 7e | CLI Commands | create page, config statistics, config locations |
| 8 | generate all | Full pipeline: scan → statistics → pages → images |
| 9 | Validate Output | index.html, images, galleries, _assets exist |
| 10 | Compress | Install compress plugin, generate compress, clean compress |
| 11 | Idempotency | clean all → generate all → generate all (incremental) |
| 12 | dotnet tool | Pack, install globally, verify version, uninstall |
| 13 | Summary | Timing report |
# Full test (recommended before release)
.\scripts\test-release.ps1
# Quick iteration (skip unit tests)
.\scripts\test-release.ps1 -SkipTests
# Test specific version
.\scripts\test-release.ps1 -Version "0.1.0-beta.1" -KeepArtifacts
# Full test including OneDrive download
.\scripts\test-release.ps1 -IncludeOneDrive
Uses samples/showcase/ as test project:
_images/, statistics page| Failure | Likely Cause | Fix |
|---|---|---|
| Step 2 Build failed | Compile error | Fix the build error, check dotnet build -c Release |
| Step 5 Pack failed (NU5026) | Missing runtimeconfig.json | Ensure dotnet build -c Release ran for that project |
| Step 5 Pack failed (NU5039) | Missing README.md | Add IsPackable=false or create README for the project |
| Step 7 Plugin install failed | Package not found in local feed | Check pack step output, verify .nupkg exists in plugins/ dir |
| Step 7b Plugin count mismatch | Plugin interface changed | Check IPlugin implementation, verify GetCommands() returns correctly |
| Step 8 generate all failed | Runtime error in pipeline | Run revela generate all manually in sample dir for full error output |
| Step 11 Idempotency failed | Clean doesn't fully reset state | Check clean all implementation, verify cache is cleared |
| Step 12 Version mismatch | -p:Version not passed to pack | Ensure both -p:Version and -p:PackageVersion are set |
Output in artifacts/release-test-{timestamp}/:
artifacts/release-test-20260311-151058/
├── cli/ # Self-contained executable + bundled Lumina
│ ├── revela.exe
│ ├── Spectara.Revela.Themes.Lumina.dll
│ └── plugins/ # Installed plugins
├── nuget/ # SDK package
├── plugins/ # Plugin/theme .nupkg files
├── tool/ # dotnet tool .nupkg
└── sample/ # Test project with generated output
├── project.json
├── source/
├── output/
└── .cache/
Typical times (Windows, with -SkipTests):