메뉴
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.
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.
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).
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.
| name | format-bump |
| description | 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. |
A format bump is the highest-risk change in this repo: it is a breaking-compat event for
every consumer and permanently adds a version the reader must support forever. Read
.claude/rules/crypto-format.md and EncryptionConstants.cs first, and confirm with the
user that a bump is truly unavoidable (many changes fit inside the current format).
SealCountMismatch), crash tolerance (Unsealed vs
RequireSealed). Get the design agreed in a GitHub issue before coding (pattern: #83).Fixtures/v<N>/ fixtures using the new-fixture skill. This is the step that cannot be
done later.FormatVersionV<N+1> to EncryptionConstants.cs, point
CurrentFormatVersion at it, add any new lengths/markers as named constants with XML
docs explaining the invariant (existing constants show the expected style).Writers/ and Readers/ symmetric.V2IntegrityTests.cs); seal/truncation semantics on both TFMs.
Run the verify-v1-compat skill — v1 must still pass untouched..claude/rules/crypto-format.md, CHANGELOG.md (breaking-changes
section with a compatibility matrix like the 6.0.0 entry), SECURITY.md if the threat
model moved, and the resources/nuget/*.md package docs.benchmark skill before/after — AAD or record layout changes hit
the per-log-event hot path.release skill when shipping).