Create a new built-in evlog enricher to add derived context to wide events. Use when adding a new enricher (e.g., for deployment metadata, tenant context,…
Scaffold a new built-in enricher for evlog with source, tests, and documentation across six mandatory touchpoints.
Enrichers follow a strict architecture: info interface, factory function returning a context mutator, header lookup, field merging with overwrite control, and early returns for missing data
Requires updates to enricher source code, test suite, built-in documentation, overview cards, public skill reference, and README enrichers table
All six touchpoints are mandatory; the skill provides a checklist, naming conventions (camelCase, PascalCase, display names), and annotated template reference
Tests must cover header population, missing headers, preserve-vs-overwrite behavior, and edge cases like empty strings and case-insensitive lookups
Create evlog Enricher
Add a new built-in enricher to evlog. Every enricher is built on the public toolkit primitive defineEnricher from evlog/toolkit — so a community enricher has the same shape as a built-in one.
PR Title
Recommended format for the pull request title:
feat: add {name} enricher
The exact wording may vary depending on the enricher (e.g., feat: add user agent enricher, feat: add geo enricher), but it should always follow the feat: conventional commit prefix.
Touchpoints Checklistdon't have the plugin yet? install it then click "run inline in claude" again.