菜单
Verify the frozen v1 fixtures are untouched and still decrypt byte-exact. Use after any change to Decrypt/Core code, before merging a branch that touches readers or the on-disk format, or when asked to check v1 backward compatibility.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run the BenchmarkDotNet suites in Example.Benchmarks and compare before/after results. Use when a change touches crypto hot paths (LogWriter, Writers/, Core) or when asked to benchmark or update README performance numbers.
Guardrailed checklist for introducing a new on-disk format version (e.g. v3). Use when a change cannot avoid altering the encrypted log wire format - new fields, different AAD, header changes, new record types.
Generate and register a frozen on-disk format fixture (encrypted .log + .expected.txt pair) for backward-compatibility testing. Use before a format-version bump to freeze the outgoing format, or when a new compat scenario needs a pinned fixture.
Cut a release - CHANGELOG finalization, GitHub Release with a MinVer semver tag, and NuGet publish verification. Use when asked to release, tag, or publish a new version (stable or preview).
| name | verify-v1-compat |
| description | Verify the frozen v1 fixtures are untouched and still decrypt byte-exact. Use after any change to Decrypt/Core code, before merging a branch that touches readers or the on-disk format, or when asked to check v1 backward compatibility. |
The v1 fixtures in tests/Serilog.Sinks.File.Decrypt.Tests/Fixtures/v1/ are the only proof
that the current reader still decrypts files written by the v5.x (v1-format) writer. This
skill checks both halves of that guarantee: the fixture bytes are unmodified, and the reader
still decrypts them byte-exact.
Fixture bytes unchanged in the working tree:
git status --porcelain -- tests/Serilog.Sinks.File.Decrypt.Tests/Fixtures/
Must print nothing. Fixtures are -text in .gitattributes, so ANY entry here is a real
byte change — stop and report it; do not commit.
Fixture bytes unchanged vs main (when on a branch):
git diff main --name-only -- tests/Serilog.Sinks.File.Decrypt.Tests/Fixtures/
Must print nothing. If a fixture differs from main, the branch has broken the compat gate.
Fixtures still decrypt byte-exact (runs on both net8.0 and net10.0):
dotnet test tests/Serilog.Sinks.File.Decrypt.Tests --filter "FullyQualifiedName~V1Fixtures"
This runs V1Fixtures_DecryptByteExact_ReportNotApplicable in V2IntegrityTests.cs,
which decrypts every fixture and compares against its .expected.txt byte-for-byte.
Report all three results explicitly. Pass = empty, empty, all tests green on both TFMs.
git restore <fixture path> / from main) — never
regenerate with the current writer. Regeneration is only valid from the 5.x release tag.