kb-update-events

Apply curatorial mutations to existing knowledge-base event records in a single batch invocation.

1|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/williamthorsen/codeassembly --skill kb-update-events-williamthorsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb-update-events
Source: https://github.com/williamthorsen/codeassembly/tree/main/packages/agents/content/skills/kb-update-events
Command: npx skills add https://github.com/williamthorsen/codeassembly --skill kb-update-events-williamthorsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Editing curatorial fields on knowledge-base events one file at a time is tedious and error-prone. This Skill batches one mutation (mark addressed-by, retag, or set impact) across multiple event records atomically, with per-event error reporting. ## Core Features & Use Cases - Batch curatorial edits: Apply one operation (--add-addressed-by, --retag, or --set-impact) to one or more event ids in a single invocation. - Registry-based store resolution: Resolves the event store by name from kb.yaml (or @default), refusing readonly stores and unregistered names. - Atomic writes with structured results: Each event is parsed to a typed KbEvent, mutated, re-validated, and written atomically; stdout reports per-event success or error codes like not-found and invalid-id. - Use Case: After triaging a recall result, mark five related events as addressed by a pull request reference in one command, then retag two of them without touching their substantive content. ## Quick Start Ask the agent to use kb-update-events to mark events <id1> and <id2> in the default store as addressed-by a given PR reference.

Frequently Asked Questions about kb-update-events

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update tags on multiple knowledge-base events at once?

Invoke the helper with --store and --retag followed by a comma-separated tag list and one or more event ids. The tags replace each event's existing tags and are canonicalized before the records are written back atomically.

How do I mark an event as addressed by a pull request or commit?

Use the --add-addressed-by flag with a reference such as a PR ref, commit SHA, URL, or KB wikilink, plus the event ids. References are stored verbatim and de-duplicated against existing entries.

Can I edit an event's summary or body with this tool?

No. This tool only handles the curatorial mutable set: addressed-by, tags, and impact. Substantive content edits to an event's summary or body must go through capture-event --amend.

Why does the helper reject combining --retag and --set-impact?

Exactly one operation flag is required per invocation; combining more than one is rejected with an invalid-args error. Run separate invocations for each operation you need to apply.

What happens if some event ids in a batch fail?

The batch is partial by design: events that succeed are written and re-validated, while failures are reported per id with error codes like not-found, invalid-id, or parse, leaving those records untouched.

What runtime is required to run the event update helper?

The bundled helper requires Node.js version 24 or later, inheriting the version floor of the @williamthorsen/kb package. The store must also be registered in kb.yaml and not marked readonly.