skills.rest
fallguyconsulting
fallguyconsultingOFFICIAL
Explore all skills by this author →
GitHub

events

Inventories structured event kinds and format violations across a codebase.

1|Updated Jul 21, 2026
Search Tags:#static analysis#code review#telemetry#naming convention#code scan#plumbline#event inventory
One-click install
npx skills add https://github.com/fallguyconsulting/ok-plugins --skill events-fallguyconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: events
Source: https://github.com/fallguyconsulting/ok-plugins/tree/main/plugins/ok/families/ok-plumbline/skills/events
Command: npx skills add https://github.com/fallguyconsulting/ok-plugins --skill events-fallguyconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate near-duplicate event kinds when developers cannot see which structured event names already exist, leading to inconsistent telemetry and fragmented observability. ## Core Features & Use Cases - Event Inventory: Runs the plumbline binary to list every event kind matching the SUBSYSTEM.NOUN.VERB convention along with every site that references it. - Format Violation Detection: Flags kind-shaped literals that break the naming convention and exits with code 2 when violations exist. - Coverage Reporting: Reports unreadable, binary, and oversized files so reviewers know which paths the scan skipped. - Use Case: Before adding a new event like BILLING.INVOICE.CREATED, run the inventory to confirm no near-duplicate kind already exists and to verify existing literals follow the convention. ## Quick Start Ask the assistant to run /ok-plumbline:events to list every event kind and format violation in the project.

Frequently Asked Questions about events

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

FAQPage Schema
How do I list all event kinds in my codebase?▼

Run the events command, which executes the plumbline binary against the project tree and prints every event kind matching the SUBSYSTEM.NOUN.VERB convention along with each site that references it.

What naming convention does the event scan enforce?▼

The convention is SUBSYSTEM.NOUN.VERB: three or more dotted segments, each starting with an upper-case letter and continuing with upper-case letters and digits. Literals matching the kind shape but breaking this rule are reported as format violations.

Does the events scan modify or fix my code?▼

No, the scan is strictly read-only. It reports the inventory and format violations but never edits code, removes kinds, or files issues; renaming violations is left to the site's author.

Why does the scan flag constants like Android intent actions?▼

The regex matches on shape alone, so dotted constants owned by other systems, such as Android intent actions or Java class names, appear as false positives. These should be left unchanged; only violations over kinds this project emits need renaming.

What does an empty event inventory mean?▼

An empty inventory means no literal in the tree matched the scan's shape. It settles nothing about convention conformance, since the scan matches only that one pattern and may skip unreadable, binary, or oversized files.

Related Skills

Explore More Software Engineering Skills→
open-gsdopen-gsd
1.0k

lint

Automate linting and formatting across a project with safe fixes.

Official
Intermediate
PostHogPostHog
713

signals-scout-feature-flags

Detects feature flag evaluation cliffs, ghost flags, distribution shifts, and flag debt in PostHog.

Official
Advanced
sage-basesage-base

plan-writer

Direct temporary implementation plans and investigation notes to the tmp/ directory.

Official
Basic
joeseesunjoeseesun
978

qiaomu-smart-search

Route user queries to suitable OpenCLI search sources via live help outputs.

Community
Intermediate