一键在 Manus 中运行任何 Skill

eventid-allocation

星标9

分支2

更新时间2026年7月8日 12:48

Manages EventId allocation for Encina structured logging — registers ranges in EventIdRanges.cs, creates *LogMessages.cs files, prevents sparses and overlaps. Triggers when adding [LoggerMessage] or structured logging to a feature.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

dlrivada

dlrivada/Encina

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

EventId Allocation Skill

Manages EventId allocation for Encina's structured logging system. Prevents collisions, sparses, and range violations.

Central Registry

Location: src/Encina/Diagnostics/EventIdRanges.cs
Format: public static readonly (int Min, int Max) RangeName = (min, max);
Discovery: EventIdRanges.GetAllRanges() returns all registered allocations

Current Range Map

Area	Range	Packages
Core	1-99	Sanitization
DomainModeling	1100-1699	Repository, UoW, Bulk, Spec, SoftDelete, Audit
Security Audit	1700-1799	Read Audit
Infrastructure	1800-1999	Tenancy, Module Isolation
Messaging	2000-2499	Outbox, Inbox, Saga, Scheduling, QueryCache, Encryption
Domain Events / ES	2500-2699	DomainEvents, AuditMarten
Security	8000-8099	Security (8000-8009), PII (8010-8029), IdGen (8030-8099)
Compliance	8100-8949	GDPR, Consent, DSR, LawfulBasis, Anonymization, CryptoShredding, Retention, DataResidency, BreachNotification, DPIA, PrivacyByDesign
Security Extensions	9000-9199	ABAC, AntiTampering
Compliance Extensions	9200-9499	NIS2, CrossBorderTransfer, ProcessorAgreements
Reserved	9500-9999	Future modules

Allocation Workflow

When adding structured logging to a feature:

Check EventIdRanges.cs for next free range in the appropriate area
Register a new public static readonly (int Min, int Max) RangeName = (min, max); with appropriate size (typically 50-100 slots)
Create Diagnostics/*LogMessages.cs with EventIds within the registered range
Update PublicAPI.Unshipped.txt for the new public field
Run architecture tests (EventIdUniquenessRule)

Rules

❌ NEVER use an EventId without registering its range first
❌ NEVER assign EventIds outside their registered range
❌ NEVER create sparses with large gaps (>10) — pack sequentially
✅ Use [LoggerMessage] source generator (NOT LoggerMessage.Define)
✅ Group EventIds by functional area within range
✅ Add XML doc comments referencing the range

Architecture Tests

Encina.Testing.Architecture.EventIdUniquenessRule provides:

Method	What It Checks
`AssertEventIdsAreGloballyUnique()`	No duplicate EventIds across assemblies
`AssertEventIdsWithinRegisteredRanges()`	Every EventId within its registered range
`AssertNoRangeOverlaps()`	No two registered ranges overlap
`GenerateAllocationReport()`	Creates human-readable table

Example

// EventIds registered in EventIdRanges.cs
public static readonly (int Min, int Max) OutboxStore = (2000, 2049);

// LogMessages.cs using EventIds in range
public static partial class LogMessages
{
    [LoggerMessage(EventId = 2001, Level = LogLevel.Information)]
    public static partial void MessageAdded(this Logger logger, Guid messageId);
}

同仓库更多 Skills

同仓库

cross-cutting-check

dlrivada/Encina

Checks that new features integrate with ALL 12 cross-cutting functions (Caching, OpenTelemetry, Logging, Health, Validation, Resilience, Distributed Locks, Transactions, Idempotency, Multi-Tenancy, Module Isolation, Audit). Triggers on new store, entity, pipeline behavior, background service, or external integration.

2026-07-089

provider-coherence

dlrivada/Encina

Ensures provider-dependent features are implemented consistently across ALL 10 DB providers (ADO.NET + Dapper + EF Core × 3 DBs + MongoDB), 8 caching, 10+ messaging transports. Triggers on new store, repository, service, or provider-specific SQL code.

2026-07-089

release-checklist

dlrivada/Encina

Validates that the codebase is ready for release — builds, passes all tests, coverage targets, PublicAPI tracking, ADRs, CHANGELOG, no warnings. Triggers when preparing a tagged release or version bump.

2026-07-089

test-workflow

dlrivada/Encina

Writes tests covering all encina test types: unit, guard, contract, property, integration. Enforces per-flag obligations model, AAA pattern, real code execution, Docker fixtures, and multi-provider coverage. Triggers on test creation or when asked to write tests.

2026-07-089

name	eventid-allocation
description	Manages EventId allocation for Encina structured logging — registers ranges in EventIdRanges.cs, creates *LogMessages.cs files, prevents sparses and overlaps. Triggers when adding [LoggerMessage] or structured logging to a feature.

EventId Allocation Skill

Manages EventId allocation for Encina's structured logging system. Prevents collisions, sparses, and range violations.

Central Registry

Location: src/Encina/Diagnostics/EventIdRanges.cs
Format: public static readonly (int Min, int Max) RangeName = (min, max);
Discovery: EventIdRanges.GetAllRanges() returns all registered allocations

Current Range Map

Area	Range	Packages
Core	1-99	Sanitization
DomainModeling	1100-1699	Repository, UoW, Bulk, Spec, SoftDelete, Audit
Security Audit	1700-1799	Read Audit
Infrastructure	1800-1999	Tenancy, Module Isolation
Messaging	2000-2499	Outbox, Inbox, Saga, Scheduling, QueryCache, Encryption
Domain Events / ES	2500-2699	DomainEvents, AuditMarten
Security	8000-8099	Security (8000-8009), PII (8010-8029), IdGen (8030-8099)
Compliance	8100-8949	GDPR, Consent, DSR, LawfulBasis, Anonymization, CryptoShredding, Retention, DataResidency, BreachNotification, DPIA, PrivacyByDesign
Security Extensions	9000-9199	ABAC, AntiTampering
Compliance Extensions	9200-9499	NIS2, CrossBorderTransfer, ProcessorAgreements
Reserved	9500-9999	Future modules

Allocation Workflow

When adding structured logging to a feature:

Check EventIdRanges.cs for next free range in the appropriate area
Register a new public static readonly (int Min, int Max) RangeName = (min, max); with appropriate size (typically 50-100 slots)
Create Diagnostics/*LogMessages.cs with EventIds within the registered range
Update PublicAPI.Unshipped.txt for the new public field
Run architecture tests (EventIdUniquenessRule)

Rules

❌ NEVER use an EventId without registering its range first
❌ NEVER assign EventIds outside their registered range
❌ NEVER create sparses with large gaps (>10) — pack sequentially
✅ Use [LoggerMessage] source generator (NOT LoggerMessage.Define)
✅ Group EventIds by functional area within range
✅ Add XML doc comments referencing the range

Architecture Tests

Encina.Testing.Architecture.EventIdUniquenessRule provides:

Method	What It Checks
`AssertEventIdsAreGloballyUnique()`	No duplicate EventIds across assemblies
`AssertEventIdsWithinRegisteredRanges()`	Every EventId within its registered range
`AssertNoRangeOverlaps()`	No two registered ranges overlap
`GenerateAllocationReport()`	Creates human-readable table

Example

// EventIds registered in EventIdRanges.cs
public static readonly (int Min, int Max) OutboxStore = (2000, 2049);

// LogMessages.cs using EventIds in range
public static partial class LogMessages
{
    [LoggerMessage(EventId = 2001, Level = LogLevel.Information)]
    public static partial void MessageAdded(this Logger logger, Guid messageId);
}