ワンクリックでManusで任意のスキルを実行

format-bump

スター7

フォーク1

更新日2026年7月6日 18:39

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 ページを確認してインストールできます。

Manusで実行

ソース

byte2pixel

byte2pixel/serilog-sinks-file-encrypt

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Introduce a new on-disk format version

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).

Checklist (in order)

Design against the threat model. Write the new layout down (AAD contents, nonce discipline, seal semantics) and check it preserves the v2 guarantees: frame reorder/splice detection, truncation fingerprinting (SealCountMismatch), crash tolerance (Unsealed vs RequireSealed). Get the design agreed in a GitHub issue before coding (pattern: #83).
Freeze the outgoing format FIRST: while the current writer still emits vN, generate Fixtures/v<N>/ fixtures using the new-fixture skill. This is the step that cannot be done later.
Constants: add 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).
Writer: emit only the new version. Keep Writers/ and Readers/ symmetric.
Reader: dispatch on the header version byte; every prior version keeps working — never delete or alter old-version read paths.
Tests: byte-exact fixture tests for the frozen vN set; integrity/tamper tests for the new version (model on V2IntegrityTests.cs); seal/truncation semantics on both TFMs. Run the verify-v1-compat skill — v1 must still pass untouched.
Docs: update .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: run the benchmark skill before/after — AAD or record layout changes hit the per-log-event hot path.
Version: this requires a major version bump (see the release skill when shipping).

このリポジトリの他の Skills

同じリポジトリ

benchmark

byte2pixel/serilog-sinks-file-encrypt

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.

2026-07-067

new-fixture

byte2pixel/serilog-sinks-file-encrypt

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.

2026-07-067

release

byte2pixel/serilog-sinks-file-encrypt

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).

2026-07-067

verify-v1-compat

byte2pixel/serilog-sinks-file-encrypt

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.

2026-07-067

Introduce a new on-disk format version

Checklist (in order)

Design against the threat model. Write the new layout down (AAD contents, nonce discipline, seal semantics) and check it preserves the v2 guarantees: frame reorder/splice detection, truncation fingerprinting (SealCountMismatch), crash tolerance (Unsealed vs RequireSealed). Get the design agreed in a GitHub issue before coding (pattern: #83).

Freeze the outgoing format FIRST: while the current writer still emits vN, generate Fixtures/v<N>/ fixtures using the new-fixture skill. This is the step that cannot be done later.

Constants: add 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).

Writer: emit only the new version. Keep Writers/ and Readers/ symmetric.

Reader: dispatch on the header version byte; every prior version keeps working — never delete or alter old-version read paths.

Tests: byte-exact fixture tests for the frozen vN set; integrity/tamper tests for the new version (model on V2IntegrityTests.cs); seal/truncation semantics on both TFMs. Run the verify-v1-compat skill — v1 must still pass untouched.

Docs: update .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: run the benchmark skill before/after — AAD or record layout changes hit the per-log-event hot path.

Version: this requires a major version bump (see the release skill when shipping).

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.