event-doc-generator

Scan Spring Boot sources to generate per-event Markdown docs and Mermaid diagrams.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/ElliotChen/ClaudeCode --skill event-doc-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-doc-generator
Source: https://github.com/ElliotChen/ClaudeCode/tree/main/skills/event-doc-generator
Command: npx skills add https://github.com/ElliotChen/ClaudeCode --skill event-doc-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The Event Documentation Generator automates the creation of comprehensive event documentation for Spring Boot projects by scanning source code to identify events, publishers, and listeners, and then generating per-event Markdown files, catalogs, and diagrams.

Core Features & Use Cases

  • Auto-scans Java sources to detect Event types, Publishers, and Listeners
  • Generates per-event Markdown docs with field details, usage notes, and context mapping
  • Produces an index/catalog and Mermaid diagrams to visualize event flows
  • Supports DDD, Event Sourcing, and Event-Driven architectures for clear documentation

Quick Start

Run the generator from the repository root to scan your codebase and output documentation under docs/event.

Frequently Asked Questions about event-doc-generator

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

FAQPage Schema
How do I generate event documentation for a Spring Boot project?

Generate event documentation for a Spring Boot project by scanning source code to identify events, publishers, and listeners. The tool outputs per-event Markdown files, a catalog, and Mermaid diagrams to visualize flows under docs/event.

Can I automatically create Mermaid diagrams for event-driven architectures?

Yes, automatically create Mermaid diagrams for event-driven architectures by scanning your codebase. The generator detects event flows and produces visual diagrams alongside Markdown documentation to map out publishers and listeners.

How do I document events and listeners in a DDD-structured system?

Document events and listeners in a DDD-structured system by scanning Java sources to extract event types and their context mappings. The tool generates detailed Markdown files with field details and usage notes for each event.

Does the event documentation generator require any specific dependencies to run?

The event documentation generator requires no specific dependencies to run. It operates deterministically by scanning your source code and uses validation hooks to ensure accurate extraction of events and listeners.

What is the best way to maintain an event catalog for Spring Boot applications?

The best way to maintain an event catalog for Spring Boot applications is automating generation via source code scanning. This approach produces an index of events and ensures documentation stays synchronized with the actual codebase.

Why are my event flows not showing up in the generated documentation?

Event flows might not show up in generated documentation if the scanner cannot identify valid publishers or listeners in your Java sources. Ensure your code follows standard Spring Boot and DDD patterns for proper detection.