Conversation
PR SummaryLow Risk Overview Updates the plugin marketplace and Release Please configuration/manifest to include the new plugin for publishing/versioning. Reviewed by Cursor Bugbot for commit 68d0461. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughAdds a new plugin Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 13
Note
Due to the large number of review comments, Critical, Major severity comments were prioritized as inline comments.
🟡 Minor comments (21)
plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/domain-patterns.md-132-132 (1)
132-132:⚠️ Potential issue | 🟡 MinorFix typo in checklist question.
Line 132 has
snaphotting; should besnapshotting.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/domain-patterns.md` at line 132, Update the misspelled checklist item text that currently reads "Is the problem snaphotting will solve?" to "Is the problem snapshotting will solve?" by editing the checklist entry string in the document (the checklist question text).plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/patterns.md-16-325 (1)
16-325:⚠️ Potential issue | 🟡 MinorAdd language identifiers to fenced code blocks.
Line 16 and other fenced blocks listed by lint are missing a language tag (
MD040). Please use```text(or another explicit language) consistently to keep docs lint-clean.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/patterns.md` around lines 16 - 325, Several fenced code blocks (e.g., the blocks showing "Aggregate: Order", the Pattern 2/3/4/5 examples and the "Stream Size Decision Tree") lack language identifiers which triggers MD040; update each triple-backtick fence to include an explicit language (recommend ```text for plain examples or a more specific tag if appropriate) so every fenced block like the ones under "Pattern 2: Composite Entity", "Pattern 3: Collection (ANTI-PATTERN)", "Pattern 4: Event Log (ANTI-PATTERN)", "Pattern 5: Historical Aggregate" and the decision tree begins with ```text (or chosen language) and ends with ```; apply consistently across the file and re-run the markdown linter to confirm MD040 is resolved.plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/snapshotting.md-23-187 (1)
23-187:⚠️ Potential issue | 🟡 MinorAdd explicit language to fenced blocks to satisfy linting.
Lines 23, 38, 49, 64, 81, 108, 139, 156, 172, and 187 trigger
MD040. Please add a language marker (e.g.,text) to each fenced block.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/snapshotting.md` around lines 23 - 187, The markdown file has multiple fenced code blocks triggering MD040; update every triple-backtick fence in this document so it includes a language marker (e.g., change ``` to ```text) for all examples/snippets (the threshold lists, decision logic examples, snapshot rules, frequency calculations and other fenced blocks) to satisfy the linter (MD040) and keep formatting consistent. Ensure you modify every fenced block in the file so the linter error is resolved.plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/domain-patterns.md-14-122 (1)
14-122:⚠️ Potential issue | 🟡 MinorSpecify fenced code block language across this reference file.
Line 14 (and the other listed fences) trigger
MD040because the code fences omit a language. Use```textfor these structured examples/checklists.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/domain-patterns.md` around lines 14 - 122, The fenced code blocks in domain-patterns.md (e.g., the initial events block under the file header and the blocks under "Shopping Cart Aggregate", "User Account Aggregate", "Account Aggregate", "Transaction Aggregate", "Loan Aggregate", "Subscription Aggregate", "User Workspace Aggregate", and "Data Collection Aggregate") are missing a language tag and trigger MD040; update every triple-backtick fence in this file to use a language identifier such as ```text so the examples/checklists are explicitly marked and the markdown linter stops reporting MD040.plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/patterns.md-16-16 (1)
16-16:⚠️ Potential issue | 🟡 MinorAdd language tags to fenced code blocks (MD040).
These unlabeled fences should be updated (e.g.,
```text) to pass markdownlint consistently.Also applies to: 79-79, 91-91, 112-112, 124-124, 140-140, 152-152, 172-172, 189-189, 203-203, 223-223, 239-239, 256-256, 270-270, 296-296, 338-338, 354-354, 366-366, 388-388, 401-401
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/patterns.md` at line 16, The Markdown contains unlabeled fenced code blocks (e.g., bare ``` fences in patterns.md) which trigger MD040; update each unlabeled fence (including instances around lines referenced) to include an explicit language tag such as ```text or a more specific language (e.g., ```json, ```yaml) so markdownlint passes; search for the triple-backtick blocks in patterns.md and replace each opening fence with an appropriate language-labeled fence while leaving the block contents unchanged.plugins/trogonstack-eventmodeling/skills/eventmodeling-integrating-legacy-systems/SKILL.md-174-174 (1)
174-174:⚠️ Potential issue | 🟡 MinorAdd language identifiers to fenced code blocks to satisfy markdownlint (MD040).
These unlabeled fences will keep lint noisy and can break strict CI doc checks. Use
text,markdown, or language-specific identifiers consistently.Minimal fix pattern
-``` +```text Traditional Approach (Risky): ... -``` +```Also applies to: 217-217, 250-250, 282-282, 328-328, 369-369, 404-404, 444-444, 611-611, 617-617, 623-623, 629-629
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-integrating-legacy-systems/SKILL.md` at line 174, The review flags unlabeled fenced code blocks in SKILL.md that trigger markdownlint MD040; update each triple-backtick fence (the unlabeled ``` blocks noted in the diff) to include a language identifier such as `text`, `markdown`, or an appropriate language token so lint passes (e.g., change ``` to ```text or ```markdown) and apply the same fix to all occurrences referenced in the comment so all unlabeled fences are consistently labeled.plugins/trogonstack-eventmodeling/skills/eventmodeling-brainstorming-events/references/facilitating-event-modeling-workshops.md-30-30 (1)
30-30:⚠️ Potential issue | 🟡 MinorFix MD040 violations by specifying languages on all fenced blocks.
Please add fence languages (
textis fine for scripts/dialogues) across these blocks to keep docs lint-clean.Also applies to: 55-55, 70-70, 87-87, 108-108, 129-129, 160-160, 172-172, 186-186, 205-205, 214-214, 230-230, 238-238, 253-253, 262-262, 271-271, 283-283, 301-301, 313-313, 325-325, 344-344, 352-352, 366-366, 375-375, 392-392, 404-404, 417-417, 427-427, 464-464, 485-485, 518-518, 560-560
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-brainstorming-events/references/facilitating-event-modeling-workshops.md` at line 30, Several fenced code blocks in facilitating-event-modeling-workshops.md are missing language tags (MD040); update each triple-backtick fence to include a language (using "text" for scripts/dialogue) so fences change from ``` to ```text for every block (the file contains many such blocks throughout — update all occurrences so the linter stops flagging MD040).plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/examples.md-64-64 (1)
64-64:⚠️ Potential issue | 🟡 MinorUse a single canonical event name for seller response publication.
SellerResponsePub.appears abbreviated while later content referencesSellerResponsePublished. Keep one event name to avoid ambiguity in slice dependencies.Also applies to: 80-80
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/examples.md` at line 64, The event list uses an abbreviated name "SellerResponsePub." while elsewhere the canonical name "SellerResponsePublished" is used; update the occurrences of "SellerResponsePub." in the examples (including the second occurrence mentioned) to "SellerResponsePublished" so all references use the single canonical event name and avoid ambiguity in slice dependencies.plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/references/security-analysis-with-event-modeling.md-159-159 (1)
159-159:⚠️ Potential issue | 🟡 MinorFill the missing sensitivity classification in the matrix row.
PaymentAuthorized | authCode |currently has an empty sensitivity value, which weakens the example’s control mapping.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/references/security-analysis-with-event-modeling.md` at line 159, The sensitivity classification for the matrix row with event "PaymentAuthorized" and data field "authCode" is missing; update that cell to a proper sensitivity level (e.g., "Confidential" or "Sensitive") so the control mapping is complete. Edit the row "PaymentAuthorized | authCode |" in the table and set the sensitivity value (choose the appropriate label used elsewhere in the document, such as "Confidential" or "Sensitive") so downstream columns like "Hidden", "Encrypted, HSM, Access log" align with that classification.plugins/trogonstack-eventmodeling/skills/eventmodeling-translating-external-events/SKILL.md-37-37 (1)
37-37:⚠️ Potential issue | 🟡 MinorAddress markdownlint issues (MD040 and MD058).
Add language specifiers to fenced blocks and surround the table with blank lines in the template section.
Also applies to: 77-77, 100-100, 130-130, 153-153, 187-187, 213-213, 293-293, 348-348, 367-367, 374-374, 381-381, 388-388, 280-280
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-translating-external-events/SKILL.md` at line 37, Fix markdownlint issues MD040 and MD058 in SKILL.md by adding language specifiers to all fenced code blocks (e.g., replace ``` with ```json, ```yaml or ```bash as appropriate) and ensure the table in the template section is surrounded by a blank line above and below it; apply the same changes to the other occurrences called out (lines referenced in the review) so every fenced block and every table has proper language tags and blank lines around tables in their respective template sections.plugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models-checklist/SKILL.md-90-90 (1)
90-90:⚠️ Potential issue | 🟡 MinorSpecify languages for fenced examples.
Add fence languages (
text/markdown) to resolve MD040 warnings.Also applies to: 97-97, 105-105, 116-116, 131-131, 149-149, 165-165, 262-262
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models-checklist/SKILL.md` at line 90, The markdown file contains multiple fenced code blocks without language tags (examples at the checklist examples around the sections referenced) which triggers MD040; update each triple-backtick fence to include an appropriate language identifier such as ```text or ```markdown for all examples (including the occurrences noted at the earlier lines and the additional ones around 97, 105, 116, 131, 149, 165, 262) so linters recognize the block language and the MD040 warnings are resolved.plugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models/SKILL.md-22-22 (1)
22-22:⚠️ Potential issue | 🟡 MinorAdd language identifiers to fenced code blocks.
These blocks should specify a language (for example
text) to satisfy MD040.Also applies to: 194-194
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models/SKILL.md` at line 22, The markdown contains fenced code blocks that use plain ``` without a language tag (notably the blocks shown as triple backticks in SKILL.md); update each fenced code block to include an appropriate language identifier (e.g., ```text or ```json) to satisfy MD040 by editing the code fences in the SKILL.md file so every ``` becomes something like ```text (or the correct language per block).plugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/references/project-planning-with-event-modeling.md-11-11 (1)
11-11:⚠️ Potential issue | 🟡 MinorClean up markdown lint violations (fence languages + heading spacing).
Add language tags to fenced blocks (MD040) and remove extra spaces after
###in headings (MD019).Also applies to: 35-35, 57-57, 84-84, 106-106, 146-146, 179-179, 193-193, 225-225, 244-244, 267-267, 275-275, 283-283, 296-296, 325-325, 265-265, 273-273, 281-281
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/references/project-planning-with-event-modeling.md` at line 11, Fix markdown-lint violations by adding language identifiers to all fenced code blocks (replace ``` with e.g. ```json, ```bash, ```text as appropriate) and remove the extra space after level-3 heading markers (convert "### Heading" from "### Heading" to single space "### Heading"); apply these fixes for every occurrence noted (the multiple fenced blocks and all headings using "###" in this document).plugins/trogonstack-eventmodeling/skills/eventmodeling-plotting-events/SKILL.md-27-27 (1)
27-27:⚠️ Potential issue | 🟡 MinorSpecify fenced code block languages.
Please annotate these blocks with explicit languages (
textis fine for ASCII examples) to resolve MD040 and improve editor rendering.Also applies to: 56-56, 70-70, 83-83
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-plotting-events/SKILL.md` at line 27, Annotate the fenced code blocks in SKILL.md with explicit languages (e.g., ```text or ```bash) to fix MD040 and improve editor rendering; locate the triple-backtick blocks currently un-annotated (seen around the example blocks at the earlier code examples) and add an appropriate language token for each (for example use text for ASCII diagrams or bash/json/js for snippets) so that the blocks at the noted positions are fenced like ```text or ```bash rather than just ```.plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/examples.md-16-16 (1)
16-16:⚠️ Potential issue | 🟡 MinorAdd language identifiers to fenced code blocks.
These fences should declare a language (for example
text,markdown,mermaid, orjson) to satisfy MD040 and keep rendering/linting consistent.Also applies to: 91-91, 102-102, 114-114, 130-130, 161-161, 181-181, 193-193, 214-214
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/examples.md` at line 16, Multiple fenced code blocks in examples.md are missing language identifiers (MD040); update each backtick-fenced block (including the one shown and also at lines referenced: 91, 102, 114, 130, 161, 181, 193, 214) to include an appropriate language tag such as "text", "markdown", "mermaid", or "json" after the opening ``` so the blocks render and lint correctly; review the content of each block to pick the correct language label and apply the change consistently across eventmodeling-slicing-event-models/references/examples.md.plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/references/security-analysis-with-event-modeling.md-15-15 (1)
15-15:⚠️ Potential issue | 🟡 MinorAdd fenced-code languages for markdown lint compliance.
These blocks should include explicit language identifiers (
text/markdown/json) to resolve MD040.Also applies to: 34-34, 56-56, 87-87, 116-116, 154-154, 168-168, 217-217, 264-264, 338-338, 375-375, 390-390
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/references/security-analysis-with-event-modeling.md` at line 15, The Markdown file contains multiple fenced code blocks using only triple backticks (```) which trigger MD040; update each fenced block (the ``` markers) to include an explicit language identifier (e.g., ```text, ```markdown or ```json) for the instances noted (occurrences listed in the review) so all code fences in security-analysis-with-event-modeling.md declare a language.plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/SKILL.md-106-106 (1)
106-106:⚠️ Potential issue | 🟡 MinorClarify prerequisite step count.
The text states "After completing full event model (Steps 1-7)" but the orchestrator defines 9 steps, with Steps 8 (Check Completeness) and 9 (Validate) being prerequisites for slicing according to the skill description. Consider updating to "After completing full event model (Steps 1-9)" or "After model validation" for clarity.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/SKILL.md` at line 106, Update the phrase "After completing full event model (Steps 1-7)" in SKILL.md to accurately reflect the orchestrator's nine-step flow; replace it with either "After completing full event model (Steps 1-9)" or "After model validation" so it matches the orchestrator steps (including Check Completeness and Validate) referenced elsewhere in the skill description.plugins/trogonstack-eventmodeling/skills/eventmodeling-designing-event-models/SKILL.md-425-425 (1)
425-425:⚠️ Potential issue | 🟡 MinorFix typo: "uncofirmed" → "unconfirmed"
Line 425 contains a spelling error in the example: "can't ship an uncofirmed order" should be "can't ship an unconfirmed order".
📝 Proposed fix
### 5. Make All Constraints Explicit Transform "obvious" business rules into documented invariants: -- "Obviously can't ship an uncofirmed order" +- "Obviously can't ship an unconfirmed order" - "ShipOrder validation: requires status='Confirmed' with paymentId"🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-designing-event-models/SKILL.md` at line 425, Replace the misspelled word "uncofirmed" with "unconfirmed" in the example string that currently reads "Obviously can't ship an uncofirmed order" (search for that exact phrase in SKILL.md or the skill content for eventmodeling-designing-event-models); update it to "Obviously can't ship an unconfirmed order" and save the markdown.plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/SKILL.md-273-285 (1)
273-285:⚠️ Potential issue | 🟡 MinorFix legend inconsistency in dependency matrix.
The legend at line 284 indicates " = Self (no external dependency)" but the table cells use "(self)" instead of the "=" symbol. Update the legend to match the table notation.
📝 Proposed fix
Legend: ← Depends on (arrow points to dependency) - = No dependency - = Self (no external dependency) + (self) = Self (no external dependency)🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/SKILL.md` around lines 273 - 285, The legend is inconsistent with the table: the table uses "(self)" for self-dependencies but the legend shows "="; update the Legend line so it matches the table notation by replacing the "=" entry with "(self) = Self (no external dependency)" (i.e., keep the existing "← Depends on..." line and change the self description to reference the "(self)" token used in the cells).plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md-344-345 (1)
344-345:⚠️ Potential issue | 🟡 MinorFix malformed markdown: heading is appended to checklist item.
Line 344 merges a checklist bullet with
## Key Principles, which breaks section structure and checklist rendering.🛠️ Proposed fix
-- [ ] **Processor failure/retry handling specified** ## Key Principles +- [ ] **Processor failure/retry handling specified** + +## Key Principles🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md` around lines 344 - 345, The checklist item and the heading are merged; split the line that currently reads "- [ ] **Processor failure/retry handling specified** ## Key Principles" into two separate lines so the checklist item stands alone ("- [ ] **Processor failure/retry handling specified**") followed by a blank line and then the heading "## Key Principles" to restore proper markdown structure in SKILL.md.plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md-343-343 (1)
343-343:⚠️ Potential issue | 🟡 MinorReplace empty symbol placeholders with explicit wording.
Line 343 currently shows empty
()placeholders for symbols, which is ambiguous for users following the checklist.🛠️ Proposed fix
-- [ ] **Automation marked with gear symbols () to distinguish from user actions ()** +- [ ] **Automation is clearly marked as processor-issued vs user-issued in all command catalogs**🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md` at line 343, Update the ambiguous empty symbol placeholders in the checklist line that reads "Automation marked with gear symbols () to distinguish from user actions ()": replace the empty parentheses with explicit symbols or words (e.g., "Automation marked with gear symbols (⚙️) to distinguish from user actions (👤)" or "Automation marked with gear symbols (automation) to distinguish from user actions (user action)"), editing the SKILL.md line containing that exact string so the checklist clearly shows which marker denotes automation vs user actions.
🧹 Nitpick comments (3)
plugins/trogonstack-eventmodeling/README.md (1)
1-7: Consider adding a quick “Included skills” section for discoverability.Install instructions are good; adding 1 short section listing key skills (or linking to
skills/) would improve first-use clarity.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/README.md` around lines 1 - 7, Add a short "Included skills" section to README.md right after the install instructions that lists the key skill names (or a single link to the skills/ directory) for discoverability; reference the repository's skills by name or path (e.g., skills/) so users can quickly see what's provided and where to find each skill.plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/SKILL.md (1)
534-534: Improve readability of completeness criteria.Line 534 concatenates three distinct criteria without clear separation: "Events are facts", "Read models are projections", and "No calculated events exist". Consider splitting into separate list items or using bullet points for better readability.
♻️ Suggested formatting improvement
Data flows logically end-to-end All stakeholder needs are met - **Events are facts (immutable domain actions)** **Read models are projections (derived/calculated state)** **No calculated events exist** (aggregations/totals are read models) + **Events are facts (immutable domain actions)** + **Read models are projections (derived/calculated state)** + **No calculated events exist** (aggregations/totals are read models) **Every role in the Role Catalog is exercised** (has commands, views, and scenarios)🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/SKILL.md` at line 534, The sentence combining three distinct completeness criteria ("Events are facts (immutable domain actions)", "Read models are projections (derived/calculated state)", and "No calculated events exist (aggregations/totals are read models)") should be split into separate, clearly delimited items for readability; update the SKILL.md content where that sentence appears to either use a bulleted list or three separate sentences/lines, each starting with the criterion phrase (e.g., "Events are facts...", "Read models are projections...", "No calculated events exist..."), preserving the parenthetical clarifications and wording exactly to avoid changing meaning.plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md (1)
39-39: Add language identifiers to fenced code blocks to satisfy markdown linting.These fences should declare a language (e.g.,
text,markdown) to resolve MD040 and improve readability in renderers.♻️ Example patch pattern
-``` +```text Storyboard: Order Creation Screen ... -``` +``` -```markdown +```markdown # Inputs: [Domain Name] ...</details> Also applies to: 58-58, 75-75, 111-111, 133-133, 162-162, 208-208, 232-232, 355-355, 368-368, 381-381 <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md
at line 39, Several fenced code blocks in SKILL.md are missing language
identifiers causing MD040 lint errors; update eachfence at the noted locations to include an appropriate language token (e.g.,text orfences around the Storyboard/Inputs examples (the ``` markers present at the comment's listed locations such as the block containing "Storyboard: Order Creation Screen" and other blocks referenced) and replace bare triple-backticks with language-qualified fences (choose text for plain narrative blocks and markdown for markdown snippets) consistently across the file.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-applying-conways-law/SKILL.md`:
- Line 154: The Markdown headings "### 6..." and "### 7..." were accidentally
merged onto the preceding paragraph; edit SKILL.md to ensure each heading (the
literal strings starting with "### 6" and "### 7") is placed on its own line
(i.e., add a newline before each "### 6..." and "### 7..." occurrence), fixing
both occurrences around the existing "Map Team Responsibilities" section so the
headings are standalone lines and restore correct document structure for
parsing.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/references/security-analysis-with-event-modeling.md`:
- Line 1: The file security-analysis-with-event-modeling.md is currently
orphaned and should be surfaced in the completeness skill: open the SKILL.md for
the eventmodeling-checking-completeness skill and add a “Reference
Documentation” section that links to or inlines the content of
security-analysis-with-event-modeling.md (ensure the link text or subsection
clearly references the security analysis doc), so the guidance is discoverable
during that skill flow.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/SKILL.md`:
- Line 511: The checklist line "- [ ] **No role in the catalog is orphaned (zero
usage across the model)** ### CRITICAL: Event vs Read Model Validation" has a
missing line break between the checklist item and the heading; edit SKILL.md so
the checklist item (the "- [ ] **No role in the catalog is orphaned (zero usage
across the model)**") ends with a newline and the "### CRITICAL: Event vs Read
Model Validation" heading starts on the next line, ensuring the checklist and
heading are separate markdown elements.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-elaborating-scenarios/SKILL.md`:
- Line 550: The checklist item and the heading are on the same line (`- [ ]
**Why behind business rules documented (not just the what)** ## Gherkin Best
Practices`); fix this by inserting a single newline immediately after the
checklist item text so the heading `## Gherkin Best Practices` starts on its own
line; locate that exact line in SKILL.md and split it into two lines (keep the
checklist text unchanged and move the heading to the following line) to restore
proper Markdown rendering.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-integrating-legacy-systems/SKILL.md`:
- Around line 628-633: Update Pattern 4 (the "Dual-Write During Transition"
block) to remove the broad dual-write recommendation and replace it with a
controlled "Mirror-Write via Integration Boundary" variant: change the heading
and body text (Pattern 4) to state dual-write is default-avoid, allow dual-write
only with an approved freeze exception, and list required controls (route
through a controlled integration boundary, make writes idempotent, add
reconciliation and rollback plan, document owner and sunset date), otherwise
instruct to keep side-car-only and sync via legacy events; target the Pattern 4
block and its text so the guideline no longer conflicts with the freeze-first
strategy.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/SKILL.md`:
- Around line 3-9: The YAML front matter's multi-line scalar starting at the
marker "description: >-" is broken because the following lines (e.g., the line
beginning "Use when concerned about stream length...") are not indented as part
of that scalar; fix it by indenting all continuation lines under "description:
>-" with at least one space (consistent indentation) so the multi-line
description is parsed correctly and the metadata block is valid.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/references/project-planning-with-event-modeling.md`:
- Around line 171-173: The comparison's numbers are inverted: the "Result: All
work done in ~22 weeks with proper parallelization" and "Without
parallelization: 13 weeks × 1 team = 13 weeks" contradict the intended
conclusion. Update the example so parallelized delivery is shorter than
non-parallelized—for example change the "Result" line to a smaller duration
(e.g., "~8–10 weeks with proper parallelization") or change the "Without
parallelization" calculation to a larger duration (e.g., "13 weeks × 2 teams =
26 weeks")—and ensure the two lines ("Result: All work done..." and "Without
parallelization: ...") are internally consistent and convey that parallelization
reduces total time.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/SKILL.md`:
- Line 196: The checklist item "[ ] All 7 modeling steps completed — no step
skipped without explicit reason" is incorrect; update it to match the workflow's
nine steps by changing "7" to "9" in SKILL.md (the checklist line string), and
scan the same file for any other references to "7 modeling steps" to update them
to "9" to keep the documentation consistent with the defined steps (Brainstorm
through Validate).
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-storyboarding-events/SKILL.md`:
- Line 404: The markdown line "- [ ] **System boundaries visible through
swimlane organization** ## Key Principles" combines a checklist and a heading;
split them by inserting a newline after the checklist item so the checklist
remains "- [ ] **System boundaries visible through swimlane organization**" and
the heading becomes its own line "## Key Principles" to restore proper Markdown
rendering in SKILL.md.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-translating-external-events/SKILL.md`:
- Around line 4-6: The YAML frontmatter "description" folded scalar is
mis-indented so the second line ("Map technical data to business concepts...")
is outside the scalar; fix by re-indenting the de-indented line to match the
folded scalar block under the description key (ensure all lines of the
description are consistently indented beneath "description:"), so the entire
text after the folded scalar indicator is part of the description frontmatter.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models-checklist/SKILL.md`:
- Around line 4-5: The document claims "23 checks" but the enumerated checklist
only contains 16 items; reconcile by either adding the seven missing checks or
updating every "23 checks" reference to the actual number used by the
enumeration. Locate the phrase "23 checks" and similar count references (e.g.,
the headings and summary lines around the enumerated list and the pass/fail
criteria), then either insert the missing check entries into the checklist so
the total becomes 23 or change all occurrences of "23" to the correct count and
update pass/fail criteria and summary wording to reflect the corrected number.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models/SKILL.md`:
- Line 154: The inline heading text is concatenated to the preceding verdict
line causing parsing errors; update SKILL.md by moving the heading "### 6.
Command State Read Models Validation (CRITICAL)" so it sits on its own line
immediately after the verdict sentence "If any command lacks actor attribution →
**REJECT MODEL — all commands must have explicit role/actor**" (i.e., insert a
newline between the verdict and the "### 6..." heading), and apply the same fix
for the analogous case around the "### 7..." heading referenced near line 190 so
each "### ..." heading is on its own line.
- Around line 16-19: The rubric uses "DDD Compliance" and aggregate-based
language that contradicts the document's Core Architectural Rule
(Non-Negotiable) which mandates that every command has its own minimal state
projection and forbids using read models for validation; update the rubric
entries (the "DDD Compliance" heading and any score descriptions referencing
"aggregate" or "aggregate roots") to use the event-sourcing terminology
instead—e.g., rename to "Projection/Command-State Compliance", replace
"aggregate" with "minimal state projection" or "read model", and rewrite scoring
text to explicitly forbid command handlers from using read models for validation
while describing the anti-patterns in terms of projections rather than DDD
aggregates (apply same change to other rubric occurrences).
---
Minor comments:
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-brainstorming-events/references/facilitating-event-modeling-workshops.md`:
- Line 30: Several fenced code blocks in
facilitating-event-modeling-workshops.md are missing language tags (MD040);
update each triple-backtick fence to include a language (using "text" for
scripts/dialogue) so fences change from ``` to ```text for every block (the file
contains many such blocks throughout — update all occurrences so the linter
stops flagging MD040).
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/references/security-analysis-with-event-modeling.md`:
- Line 159: The sensitivity classification for the matrix row with event
"PaymentAuthorized" and data field "authCode" is missing; update that cell to a
proper sensitivity level (e.g., "Confidential" or "Sensitive") so the control
mapping is complete. Edit the row "PaymentAuthorized | authCode |" in the table
and set the sensitivity value (choose the appropriate label used elsewhere in
the document, such as "Confidential" or "Sensitive") so downstream columns like
"Hidden", "Encrypted, HSM, Access log" align with that classification.
- Line 15: The Markdown file contains multiple fenced code blocks using only
triple backticks (```) which trigger MD040; update each fenced block (the ```
markers) to include an explicit language identifier (e.g., ```text, ```markdown
or ```json) for the instances noted (occurrences listed in the review) so all
code fences in security-analysis-with-event-modeling.md declare a language.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-designing-event-models/SKILL.md`:
- Line 425: Replace the misspelled word "uncofirmed" with "unconfirmed" in the
example string that currently reads "Obviously can't ship an uncofirmed order"
(search for that exact phrase in SKILL.md or the skill content for
eventmodeling-designing-event-models); update it to "Obviously can't ship an
unconfirmed order" and save the markdown.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md`:
- Around line 344-345: The checklist item and the heading are merged; split the
line that currently reads "- [ ] **Processor failure/retry handling specified**
## Key Principles" into two separate lines so the checklist item stands alone
("- [ ] **Processor failure/retry handling specified**") followed by a blank
line and then the heading "## Key Principles" to restore proper markdown
structure in SKILL.md.
- Line 343: Update the ambiguous empty symbol placeholders in the checklist line
that reads "Automation marked with gear symbols () to distinguish from user
actions ()": replace the empty parentheses with explicit symbols or words (e.g.,
"Automation marked with gear symbols (⚙️) to distinguish from user actions (👤)"
or "Automation marked with gear symbols (automation) to distinguish from user
actions (user action)"), editing the SKILL.md line containing that exact string
so the checklist clearly shows which marker denotes automation vs user actions.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-integrating-legacy-systems/SKILL.md`:
- Line 174: The review flags unlabeled fenced code blocks in SKILL.md that
trigger markdownlint MD040; update each triple-backtick fence (the unlabeled ```
blocks noted in the diff) to include a language identifier such as `text`,
`markdown`, or an appropriate language token so lint passes (e.g., change ``` to
```text or ```markdown) and apply the same fix to all occurrences referenced in
the comment so all unlabeled fences are consistently labeled.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/domain-patterns.md`:
- Line 132: Update the misspelled checklist item text that currently reads "Is
the problem snaphotting will solve?" to "Is the problem snapshotting will
solve?" by editing the checklist entry string in the document (the checklist
question text).
- Around line 14-122: The fenced code blocks in domain-patterns.md (e.g., the
initial events block under the file header and the blocks under "Shopping Cart
Aggregate", "User Account Aggregate", "Account Aggregate", "Transaction
Aggregate", "Loan Aggregate", "Subscription Aggregate", "User Workspace
Aggregate", and "Data Collection Aggregate") are missing a language tag and
trigger MD040; update every triple-backtick fence in this file to use a language
identifier such as ```text so the examples/checklists are explicitly marked and
the markdown linter stops reporting MD040.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/patterns.md`:
- Around line 16-325: Several fenced code blocks (e.g., the blocks showing
"Aggregate: Order", the Pattern 2/3/4/5 examples and the "Stream Size Decision
Tree") lack language identifiers which triggers MD040; update each
triple-backtick fence to include an explicit language (recommend ```text for
plain examples or a more specific tag if appropriate) so every fenced block like
the ones under "Pattern 2: Composite Entity", "Pattern 3: Collection
(ANTI-PATTERN)", "Pattern 4: Event Log (ANTI-PATTERN)", "Pattern 5: Historical
Aggregate" and the decision tree begins with ```text (or chosen language) and
ends with ```; apply consistently across the file and re-run the markdown linter
to confirm MD040 is resolved.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/snapshotting.md`:
- Around line 23-187: The markdown file has multiple fenced code blocks
triggering MD040; update every triple-backtick fence in this document so it
includes a language marker (e.g., change ``` to ```text) for all
examples/snippets (the threshold lists, decision logic examples, snapshot rules,
frequency calculations and other fenced blocks) to satisfy the linter (MD040)
and keep formatting consistent. Ensure you modify every fenced block in the file
so the linter error is resolved.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/references/project-planning-with-event-modeling.md`:
- Line 11: Fix markdown-lint violations by adding language identifiers to all
fenced code blocks (replace ``` with e.g. ```json, ```bash, ```text as
appropriate) and remove the extra space after level-3 heading markers (convert
"### Heading" from "### Heading" to single space "### Heading"); apply these
fixes for every occurrence noted (the multiple fenced blocks and all headings
using "###" in this document).
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-plotting-events/SKILL.md`:
- Line 27: Annotate the fenced code blocks in SKILL.md with explicit languages
(e.g., ```text or ```bash) to fix MD040 and improve editor rendering; locate the
triple-backtick blocks currently un-annotated (seen around the example blocks at
the earlier code examples) and add an appropriate language token for each (for
example use text for ASCII diagrams or bash/json/js for snippets) so that the
blocks at the noted positions are fenced like ```text or ```bash rather than
just ```.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/examples.md`:
- Line 64: The event list uses an abbreviated name "SellerResponsePub." while
elsewhere the canonical name "SellerResponsePublished" is used; update the
occurrences of "SellerResponsePub." in the examples (including the second
occurrence mentioned) to "SellerResponsePublished" so all references use the
single canonical event name and avoid ambiguity in slice dependencies.
- Line 16: Multiple fenced code blocks in examples.md are missing language
identifiers (MD040); update each backtick-fenced block (including the one shown
and also at lines referenced: 91, 102, 114, 130, 161, 181, 193, 214) to include
an appropriate language tag such as "text", "markdown", "mermaid", or "json"
after the opening ``` so the blocks render and lint correctly; review the
content of each block to pick the correct language label and apply the change
consistently across eventmodeling-slicing-event-models/references/examples.md.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/patterns.md`:
- Line 16: The Markdown contains unlabeled fenced code blocks (e.g., bare ```
fences in patterns.md) which trigger MD040; update each unlabeled fence
(including instances around lines referenced) to include an explicit language
tag such as ```text or a more specific language (e.g., ```json, ```yaml) so
markdownlint passes; search for the triple-backtick blocks in patterns.md and
replace each opening fence with an appropriate language-labeled fence while
leaving the block contents unchanged.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/SKILL.md`:
- Line 106: Update the phrase "After completing full event model (Steps 1-7)" in
SKILL.md to accurately reflect the orchestrator's nine-step flow; replace it
with either "After completing full event model (Steps 1-9)" or "After model
validation" so it matches the orchestrator steps (including Check Completeness
and Validate) referenced elsewhere in the skill description.
- Around line 273-285: The legend is inconsistent with the table: the table uses
"(self)" for self-dependencies but the legend shows "="; update the Legend line
so it matches the table notation by replacing the "=" entry with "(self) = Self
(no external dependency)" (i.e., keep the existing "← Depends on..." line and
change the self description to reference the "(self)" token used in the cells).
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-translating-external-events/SKILL.md`:
- Line 37: Fix markdownlint issues MD040 and MD058 in SKILL.md by adding
language specifiers to all fenced code blocks (e.g., replace ``` with ```json,
```yaml or ```bash as appropriate) and ensure the table in the template section
is surrounded by a blank line above and below it; apply the same changes to the
other occurrences called out (lines referenced in the review) so every fenced
block and every table has proper language tags and blank lines around tables in
their respective template sections.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models-checklist/SKILL.md`:
- Line 90: The markdown file contains multiple fenced code blocks without
language tags (examples at the checklist examples around the sections
referenced) which triggers MD040; update each triple-backtick fence to include
an appropriate language identifier such as ```text or ```markdown for all
examples (including the occurrences noted at the earlier lines and the
additional ones around 97, 105, 116, 131, 149, 165, 262) so linters recognize
the block language and the MD040 warnings are resolved.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models/SKILL.md`:
- Line 22: The markdown contains fenced code blocks that use plain ``` without a
language tag (notably the blocks shown as triple backticks in SKILL.md); update
each fenced code block to include an appropriate language identifier (e.g.,
```text or ```json) to satisfy MD040 by editing the code fences in the SKILL.md
file so every ``` becomes something like ```text (or the correct language per
block).
---
Nitpick comments:
In `@plugins/trogonstack-eventmodeling/README.md`:
- Around line 1-7: Add a short "Included skills" section to README.md right
after the install instructions that lists the key skill names (or a single link
to the skills/ directory) for discoverability; reference the repository's skills
by name or path (e.g., skills/) so users can quickly see what's provided and
where to find each skill.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/SKILL.md`:
- Line 534: The sentence combining three distinct completeness criteria ("Events
are facts (immutable domain actions)", "Read models are projections
(derived/calculated state)", and "No calculated events exist
(aggregations/totals are read models)") should be split into separate, clearly
delimited items for readability; update the SKILL.md content where that sentence
appears to either use a bulleted list or three separate sentences/lines, each
starting with the criterion phrase (e.g., "Events are facts...", "Read models
are projections...", "No calculated events exist..."), preserving the
parenthetical clarifications and wording exactly to avoid changing meaning.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md`:
- Line 39: Several fenced code blocks in SKILL.md are missing language
identifiers causing MD040 lint errors; update each ``` fence at the noted
locations to include an appropriate language token (e.g., ```text or
```markdown) so renderers and the linter recognize the block type. Edit the code
fences around the Storyboard/Inputs examples (the ``` markers present at the
comment's listed locations such as the block containing "Storyboard: Order
Creation Screen" and other blocks referenced) and replace bare triple-backticks
with language-qualified fences (choose text for plain narrative blocks and
markdown for markdown snippets) consistently across the file.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: a3fe76c3-c0bf-4eb1-b1eb-63584de62a93
📒 Files selected for processing (29)
.claude-plugin/marketplace.json.github/release-please-config.json.github/release-please-manifest.jsonplugins/trogonstack-eventmodeling/.claude-plugin/plugin.jsonplugins/trogonstack-eventmodeling/README.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-applying-conways-law/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-brainstorming-events/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-brainstorming-events/references/facilitating-event-modeling-workshops.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/references/security-analysis-with-event-modeling.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-designing-event-models/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-elaborating-scenarios/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-outputs/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-integrating-legacy-systems/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/domain-patterns.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/patterns.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/snapshotting.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/references/project-planning-with-event-modeling.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-plotting-events/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/examples.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/patterns.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-storyboarding-events/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-translating-external-events/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models-checklist/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models/SKILL.md
plugins/trogonstack-eventmodeling/skills/eventmodeling-applying-conways-law/SKILL.md
Show resolved
Hide resolved
...ills/eventmodeling-checking-completeness/references/security-analysis-with-event-modeling.md
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/SKILL.md
Outdated
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-elaborating-scenarios/SKILL.md
Outdated
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-integrating-legacy-systems/SKILL.md
Outdated
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-storyboarding-events/SKILL.md
Outdated
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-translating-external-events/SKILL.md
Show resolved
Hide resolved
...ns/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models-checklist/SKILL.md
Outdated
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models/SKILL.md
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models/SKILL.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/SKILL.md`:
- Around line 21-73: The fenced code blocks in SKILL.md (e.g., the Event:
OrderCreated block and the other event/field blocks shown in the diff) are
missing language specifiers which triggers MD040; update each triple-backtick
fence to include a language token (e.g., ```text or ```markdown) for the blocks
starting around the Event: OrderCreated section and the other blocks referenced
(lines noted in the review: 21, 78, 103, 132, 156, 186, 234, 257, 303, 320) so
every fenced block has a language indicator.
- Around line 3-8: The YAML frontmatter under the description key in SKILL.md is
broken because lines after "description: >-" (notably the lines starting with
"Ensure complete event model..." and "Given-When-Then specs...") are not
indented into the folded scalar; fix by indenting all lines that belong to the
description block (i.e., every line intended to be part of the folded scalar) by
two spaces under the "description: >-" entry so they are included in the folded
scalar and the frontmatter parses correctly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: be1668e4-a057-469c-977c-b5d7df77aeb3
📒 Files selected for processing (1)
plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/SKILL.md
plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/SKILL.md
Outdated
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/SKILL.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Actionable comments posted: 2
♻️ Duplicate comments (2)
plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/SKILL.md (2)
5-8:⚠️ Potential issue | 🔴 CriticalCritical: Fix invalid YAML frontmatter indentation.
Lines 5 and 8 are not indented under the folded scalar
>-started at line 3, which will break frontmatter parsing.🐛 Proposed fix
description: >- Final step - Completeness Check. Verify every field has origin and destination. - Ensure complete event model before code generation. Use after all scenarios + Ensure complete event model before code generation. Use after all scenarios defined. Do not use for: architectural validation against event sourcing principles (use eventmodeling-validating-event-models) or elaborating - Given-When-Then specs (use eventmodeling-elaborating-scenarios). + Given-When-Then specs (use eventmodeling-elaborating-scenarios).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/SKILL.md` around lines 5 - 8, The YAML frontmatter folded scalar started with the marker `>-` (in SKILL.md) has lines that are not indented into the block (the content on lines 5 and 8), causing the frontmatter parser to break; fix this by indenting those lines so they are children of the `>-` folded scalar (match the indentation of the other block lines), ensuring all lines intended as part of the folded scalar are consistently indented under the `>-` marker.
511-511:⚠️ Potential issue | 🔴 CriticalCritical: Fix missing line break before heading.
Line 511 has a checklist item and heading on the same line:
- [ ] **No role in the catalog is orphaned (zero usage across the model)** ### CRITICAL: Event vs Read Model Validation. This will break markdown rendering.🐛 Proposed fix
-- [ ] **No role in the catalog is orphaned (zero usage across the model)** ### CRITICAL: Event vs Read Model Validation +- [ ] **No role in the catalog is orphaned (zero usage across the model)** + +### CRITICAL: Event vs Read Model Validation🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/SKILL.md` at line 511, The markdown has a checklist item and a heading combined on one line (`- [ ] **No role in the catalog is orphaned (zero usage across the model)** ### CRITICAL: Event vs Read Model Validation`); split them by inserting a newline before the heading so the checklist remains on its own line and the `### CRITICAL: Event vs Read Model Validation` becomes a separate heading line (update the line containing that exact string in SKILL.md).
🧹 Nitpick comments (5)
plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/SKILL.md (1)
68-73: Add language identifiers to fenced code blocks to satisfy markdownlint.Line 68, Line 138, and Line 160 open fenced blocks without a language, which triggers MD040 and can fail docs linting pipelines.
Proposed fix
-``` +```text Estimated Stream Length = Events Per Aggregate Instance × Lifetime of Instance (years) × Annual Growth Factor```diff -``` +```text Before implementing snapshotting, ask: ... Only after exhausting design improvements, consider snapshots.```diff -``` +```text Snapshotting Complexity ≈ 2-3x Complexity of Better Design ... Better to redesign and keep streams < 300 events.</details> Also applies to: 138-156, 160-167 <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/SKILL.md
around lines 68 - 73, Three fenced code blocks (the one starting with "Estimated
Stream Length =", the "Before implementing snapshotting, ask:" checklist, and
the "Snapshotting Complexity ≈ 2-3x Complexity of Better Design" note) lack
language identifiers, causing markdownlint MD040 failures; add a language tag
(e.g.,text) to each opening fence so they readtext rather than ``` to
satisfy the linter while preserving content and formatting.</details> </blockquote></details> <details> <summary>plugins/trogonstack-eventmodeling/skills/eventmodeling-translating-external-events/SKILL.md (1)</summary><blockquote> `37-71`: **Consider adding language specifiers to fenced code blocks.** Multiple fenced code blocks throughout the workflow section lack language specifiers, which reduces syntax highlighting and readability. Adding appropriate specifiers would improve the documentation quality. **Suggested language specifiers:** - Lines 37-71: Use ` ```json ` for JSON payload examples - Lines 77-94, 100-124, 130-147: Use ` ```text ` for structured technical analysis - Lines 153-181, 187-207, 213-243: Use ` ```text ` for scenario descriptions As per static analysis hints, markdownlint recommends specifying languages for all fenced code blocks (MD040). Also applies to: 77-94, 100-124, 130-147, 153-181, 187-207, 213-243 <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@plugins/trogonstack-eventmodeling/skills/eventmodeling-translating-external-events/SKILL.md
around lines 37 - 71, Update the fenced code blocks in SKILL.md to include
language specifiers: change the JSON payload examples (e.g., the
"charge.succeeded" payload and the "geofence_exit" payload) to usejson and change the structured technical analysis and scenario description blocks (the other workflow sections mentioned) to usetext so markdownlint MD040 is
satisfied and syntax highlighting/readability is improved.</details> </blockquote></details> <details> <summary>plugins/trogonstack-eventmodeling/skills/eventmodeling-brainstorming-events/SKILL.md (1)</summary><blockquote> `135-144`: **Consider adding language specifier to fenced code block.** While not flagged by static analysis, the fenced code block showing example brainstormed events would benefit from a language specifier (e.g., `text`) for consistency with best practices. <details> <summary>♻️ Proposed fix</summary> ```diff Participants call out events (sticky notes or digital cards): -``` +```text "Customer places order" ``` </details> <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@plugins/trogonstack-eventmodeling/skills/eventmodeling-brainstorming-events/SKILL.md
around lines 135 - 144, The fenced code block containing the brainstormed events
(the block starting withand listing "Customer places order", "Order confirmed", etc.) should include a language specifier for clarity and consistency; update that block to use a specifier liketext so the events are
fenced astext ..., ensuring the code fence around the event list (the
multi-line string entries) is changed accordingly.</details> </blockquote></details> <details> <summary>plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/SKILL.md (1)</summary><blockquote> `44-53`: **Add language specifier to fenced code block.** The fenced code block lacks a language specifier, which triggers MD040. Consider adding `text` or an appropriate language identifier for better tooling support. <details> <summary>♻️ Proposed fix</summary> ```diff -``` +```text If user has provided: ``` </details> **Note**: This recommendation applies to all fenced code blocks in the file (lines 44, 128, 150, 165, 187, 219, 249, 273, 293, 317). <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/SKILL.md
around lines 44 - 53, The fenced code blocks in SKILL.md (e.g., the block
starting with "If user has provided:" and the other blocks at the indicated
occurrences) are missing a language specifier which triggers MD040; update each
triple-backtick fence to include a neutral specifier like text (e.g., changetotext) for every fenced block mentioned (lines containing the snippets
starting "If user has provided:", and the other blocks at the listed locations)
so tooling recognizes them; ensure you apply the same change to all instances in
the file.</details> </blockquote></details> <details> <summary>plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md (1)</summary><blockquote> `39-53`: **Add language specifier to fenced code block.** The fenced code block lacks a language specifier, which triggers MD040. Consider adding `text` or an appropriate language identifier. <details> <summary>♻️ Proposed fix</summary> ```diff -``` +```text Storyboard: Order Creation Screen ``` </details> **Note**: This recommendation applies to all fenced code blocks in the file (lines 39, 58, 75, 111, 133, 162, 208, 232, 355, 368, 381). Adding language specifiers improves tooling support and rendering consistency. <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md
around lines 39 - 53, The Markdown fenced code blocks (e.g., the block starting
with "Storyboard: Order Creation Screen") lack a language specifier which
triggers MD040; update each triple-backtick fence to include a language
identifier (for example ```text) for all such blocks in SKILL.md (notably the
blocks containing "Storyboard: Order Creation Screen" and the other similar
storyboard/code snippets) so tooling renders them correctly.</details> </blockquote></details> </blockquote></details> <details> <summary>🤖 Prompt for all review comments with AI agents</summary>Verify each finding against the current code and only fix it if needed.
Inline comments:
In
@plugins/trogonstack-eventmodeling/skills/eventmodeling-brainstorming-events/SKILL.md:
- Around line 286-300: Remove the duplicate top-level heading by deleting the
first occurrence of "# Domain Analysis: [Domain Name]" that appears immediately
before "## Workshop Notes" so the template contains a single "# Domain Analysis:
[Domain Name]" (the remaining one after the workshop notes); ensure the "##
Workshop Notes" section stays intact and only the redundant heading is removed.In
@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md:
- Line 344: The markdown has a combined checklist item and heading on one line:
"- [ ] Processor failure/retry handling specified ## Key Principles"; split
them into two separate lines so the checklist item ends on its own line and the
"## Key Principles" heading is on the following line to restore proper Markdown
rendering (edit the SKILL.md content around the string "Processor
failure/retry handling specified" to insert a newline before "## Key
Principles").
Duplicate comments:
In
@plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/SKILL.md:
- Around line 5-8: The YAML frontmatter folded scalar started with the marker
>-(in SKILL.md) has lines that are not indented into the block (the content
on lines 5 and 8), causing the frontmatter parser to break; fix this by
indenting those lines so they are children of the>-folded scalar (match the
indentation of the other block lines), ensuring all lines intended as part of
the folded scalar are consistently indented under the>-marker.- Line 511: The markdown has a checklist item and a heading combined on one line
(- [ ] **No role in the catalog is orphaned (zero usage across the model)** ### CRITICAL: Event vs Read Model Validation); split them by inserting a newline
before the heading so the checklist remains on its own line and the### CRITICAL: Event vs Read Model Validationbecomes a separate heading line
(update the line containing that exact string in SKILL.md).
Nitpick comments:
In
@plugins/trogonstack-eventmodeling/skills/eventmodeling-brainstorming-events/SKILL.md:
- Around line 135-144: The fenced code block containing the brainstormed events
(the block starting withand listing "Customer places order", "Order confirmed", etc.) should include a language specifier for clarity and consistency; update that block to use a specifier liketext so the events are
fenced astext ..., ensuring the code fence around the event list (the
multi-line string entries) is changed accordingly.In
@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md:
- Around line 39-53: The Markdown fenced code blocks (e.g., the block starting
with "Storyboard: Order Creation Screen") lack a language specifier which
triggers MD040; update each triple-backtick fence to include a language
identifier (for example ```text) for all such blocks in SKILL.md (notably the
blocks containing "Storyboard: Order Creation Screen" and the other similar
storyboard/code snippets) so tooling renders them correctly.In
@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/SKILL.md:
- Around line 68-73: Three fenced code blocks (the one starting with "Estimated
Stream Length =", the "Before implementing snapshotting, ask:" checklist, and
the "Snapshotting Complexity ≈ 2-3x Complexity of Better Design" note) lack
language identifiers, causing markdownlint MD040 failures; add a language tag
(e.g.,text) to each opening fence so they readtext rather than ``` to
satisfy the linter while preserving content and formatting.In
@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/SKILL.md:
- Around line 44-53: The fenced code blocks in SKILL.md (e.g., the block
starting with "If user has provided:" and the other blocks at the indicated
occurrences) are missing a language specifier which triggers MD040; update each
triple-backtick fence to include a neutral specifier like text (e.g., changetotext) for every fenced block mentioned (lines containing the snippets
starting "If user has provided:", and the other blocks at the listed locations)
so tooling recognizes them; ensure you apply the same change to all instances in
the file.In
@plugins/trogonstack-eventmodeling/skills/eventmodeling-translating-external-events/SKILL.md:
- Around line 37-71: Update the fenced code blocks in SKILL.md to include
language specifiers: change the JSON payload examples (e.g., the
"charge.succeeded" payload and the "geofence_exit" payload) to usejson and change the structured technical analysis and scenario description blocks (the other workflow sections mentioned) to usetext so markdownlint MD040 is
satisfied and syntax highlighting/readability is improved.</details> <details> <summary>🪄 Autofix (Beta)</summary> Fix all unresolved CodeRabbit comments on this PR: - [ ] <!-- {"checkboxId": "4b0d0e0a-96d7-4f10-b296-3a18ea78f0b9"} --> Push a commit to this branch (recommended) - [ ] <!-- {"checkboxId": "ff5b1114-7d8c-49e6-8ac1-43f82af23a33"} --> Create a new PR with the fixes </details> --- <details> <summary>ℹ️ Review info</summary> <details> <summary>⚙️ Run configuration</summary> **Configuration used**: Organization UI **Review profile**: CHILL **Plan**: Pro **Run ID**: `5e030b8b-b142-4c61-b1f7-50b1ac8c2511` </details> <details> <summary>📥 Commits</summary> Reviewing files that changed from the base of the PR and between b5bee695e1d86fe1804930debeb013271d032898 and e995924e67e984c68e51be9c760a198279e6be2c. </details> <details> <summary>📒 Files selected for processing (7)</summary> * `plugins/trogonstack-eventmodeling/skills/eventmodeling-brainstorming-events/SKILL.md` * `plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/SKILL.md` * `plugins/trogonstack-eventmodeling/skills/eventmodeling-elaborating-scenarios/SKILL.md` * `plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md` * `plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/SKILL.md` * `plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/SKILL.md` * `plugins/trogonstack-eventmodeling/skills/eventmodeling-translating-external-events/SKILL.md` </details> <details> <summary>✅ Files skipped from review due to trivial changes (1)</summary> * plugins/trogonstack-eventmodeling/skills/eventmodeling-elaborating-scenarios/SKILL.md </details> </details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
plugins/trogonstack-eventmodeling/skills/eventmodeling-brainstorming-events/SKILL.md
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md
Outdated
Show resolved
Hide resolved
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md
Outdated
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-applying-conways-law/SKILL.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Actionable comments posted: 6
Note
Due to the large number of review comments, Critical, Major severity comments were prioritized as inline comments.
♻️ Duplicate comments (3)
plugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/references/project-planning-with-event-modeling.md (1)
162-163:⚠️ Potential issue | 🟠 MajorFix contradictory parallelization comparison numbers.
The section currently states parallelized delivery is
~22 weekswhile “without parallelization” is13 weeks, which reverses the intended conclusion. This needs a consistent, corrected comparison.Proposed fix
- TOTAL 13 4 sprints ~22 weeks + TOTAL 13 4.3 sprints ~13 weeks ... -Result: All work done in ~22 weeks with proper parallelization -Without parallelization: 13 weeks × 1 team = 13 weeks (but no parallelization possible with tight coupling) +Result: All work done in ~13 weeks with proper parallelization +Without parallelization: ~39 weeks with 1 team (same scope done sequentially)Also applies to: 171-173
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/references/project-planning-with-event-modeling.md` around lines 162 - 163, The document shows contradictory totals: the line "TOTAL 13 4 sprints ~22 weeks" (and the other occurrence at 171–173) mixes a 13 and ~22 in a way that reverses the intended conclusion; update these two places so the "without parallelization" case reflects the longer duration (~22 weeks) and the "with parallelization" case reflects the shorter duration (~13 weeks) — i.e., swap/correct the numeric totals so the parallelized delivery is ~13 weeks and the non-parallelized delivery is ~22 weeks consistently.plugins/trogonstack-eventmodeling/skills/eventmodeling-storyboarding-events/SKILL.md (1)
404-406:⚠️ Potential issue | 🟠 MajorSplit checklist item and heading onto separate lines (rendering break).
## Key Principlesis still appended to the checklist line, which breaks section structure.Proposed fix
-- [ ] **System boundaries visible through swimlane organization** ## Key Principles +- [ ] **System boundaries visible through swimlane organization** + +## Key Principles🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-storyboarding-events/SKILL.md` around lines 404 - 406, The checklist line currently contains the heading appended to it; locate the line containing "- [ ] **System boundaries visible through swimlane organization** ## Key Principles" and split it into two separate lines so the checklist stays on its own and "## Key Principles" becomes a standalone heading on the next line, preserving surrounding formatting and spacing.plugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models-checklist/SKILL.md (1)
4-5:⚠️ Potential issue | 🟠 MajorChecklist count is still inconsistent (23 claimed vs 16 defined).
Line 4/15/26 and later sections still state “23 checks,” but the listed checks add up to 16. Please reconcile the count or add the missing checks so scoring and completion criteria are reliable.
Also applies to: 15-16, 26-27, 210-212, 284-285, 316-317, 337-337
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models-checklist/SKILL.md` around lines 4 - 5, The SKILL.md Claim "23 checks" is inconsistent with the actual checklist items (16); update the document so the claimed number matches the defined checks: either add the missing 7 checks to the checklist or change every occurrence of "23 checks"/"23" to the correct total, and ensure the scoring/completion criteria and any summary sections (the lead sentence "Validate event-sourced CQRS models...", the checklist summary lines that repeat the count, and the scoring/completion paragraphs) reflect the same, reconciled count so totals and scoring logic are consistent across the file.
🟡 Minor comments (22)
plugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/references/project-planning-with-event-modeling.md-11-11 (1)
11-11:⚠️ Potential issue | 🟡 MinorResolve markdownlint violations (fence languages and heading spacing).
MD040 and MD019 warnings are valid here: add language identifiers to fenced blocks and remove double spaces after
###headings.Example fixes
-``` +```text Feature Cost-### Mistake 1: Counting All Features as Equal Weight +### Mistake 1: Counting All Features as Equal WeightAlso applies to: 35-35, 57-57, 84-84, 106-106, 146-146, 179-179, 193-193, 225-225, 244-244, 265-265, 267-267, 273-273, 275-275, 281-281, 283-283, 296-296, 325-325
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/references/project-planning-with-event-modeling.md` at line 11, Fix markdownlint MD040 and MD019 in project-planning-with-event-modeling.md by adding language identifiers to all fenced code blocks (e.g., change ``` to ```text or appropriate language) and removing the extra double space after "###" headings so they use single space (e.g., "### Heading" not "### Heading"); apply these changes to the mentioned code fences and headings (lines referenced: 11, 35, 57, 84, 106, 146, 179, 193, 225, 244, 265, 267, 273, 275, 281, 283, 296, 325) and verify markdownlint no longer reports MD040/MD019.plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/snapshotting.md-48-48 (1)
48-48:⚠️ Potential issue | 🟡 MinorAdd a language to the fenced block.
Line 48 opens a fenced code block without a language; use
textfor consistency with docs lint rules.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/snapshotting.md` at line 48, The fenced code block opened immediately after the heading "**Question 2: What's your read latency requirement?**" is missing a language specifier; update the opening fence from ``` to ```text so the block is marked as text (e.g., change the triple backticks that start that code block to ```text) to satisfy docs lint rules.plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/domain-patterns.md-14-14 (1)
14-14:⚠️ Potential issue | 🟡 MinorSpecify language on fenced blocks for lint compliance.
Line 14, Line 24, Line 34, Line 48, Line 59, Line 69, Line 84, Line 94, Line 104, and Line 122 should include a fence language (
textis fine for these examples).Also applies to: 24-24, 34-34, 48-48, 59-59, 69-69, 84-84, 94-94, 104-104, 122-122
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/domain-patterns.md` at line 14, Update the fenced code blocks in domain-patterns.md to include a language identifier (e.g., add ```text instead of just ```) for each fenced block referenced (the blocks at the positions noted in the review: lines 14, 24, 34, 48, 59, 69, 84, 94, 104, and 122) so they comply with the linter; simply edit each opening triple-backtick to include "text" (```text) and leave the block contents unchanged.plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/SKILL.md-68-68 (1)
68-68:⚠️ Potential issue | 🟡 MinorAdd fenced code block languages for markdownlint compliance.
Line 68, Line 138, and Line 160 should specify a language (
textworks for all three blocks).Also applies to: 138-138, 160-160
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/SKILL.md` at line 68, The markdown in SKILL.md contains three fenced code blocks that are missing language identifiers (the blocks around the examples at the three spots called out in the review); to satisfy markdownlint, open each triple-backtick fence and add a language token (use "text") so they read ```text, ensuring all three blocks are updated consistently to remove the lint warnings.plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/patterns.md-16-16 (1)
16-16:⚠️ Potential issue | 🟡 MinorAdd fence languages to satisfy markdownlint and improve rendering consistency.
Line 16, Line 44, Line 82, Line 119, Line 158, Line 196, Line 252, Line 289, Line 296, Line 304, Line 316, and Line 325 open fenced blocks without a language. Use
text(oryamlwhere applicable).🛠️ Suggested pattern
-``` +```text ... -``` +```Also applies to: 44-44, 82-82, 119-119, 158-158, 196-196, 252-252, 289-289, 296-296, 304-304, 316-316, 325-325
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/patterns.md` at line 16, Update all fenced code blocks opened with ``` to include a language identifier to satisfy markdownlint and improve rendering: replace the bare fences at the reported locations (all occurrences where a block starts with ``` on lines like 16, 44, 82, 119, 158, 196, 252, 289, 296, 304, 316, 325) with ```text for plain text blocks or ```yaml where the content is YAML; ensure each opening fence matches its closing ``` so rendering and linting pass.plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/domain-patterns.md-132-132 (1)
132-132:⚠️ Potential issue | 🟡 MinorFix typo in checklist question.
Line 132 has
snaphotting; this should besnapshotting.✏️ Suggested fix
-[ ] Is the problem snaphotting will solve? +[ ] Is the problem snapshotting will solve?🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/domain-patterns.md` at line 132, Fix the typo in the checklist question by replacing the misspelled token "snaphotting" with the correct "snapshotting" in the checklist line containing "[ ] Is the problem snaphotting will solve?" so the line reads "[ ] Is the problem snapshotting will solve?" and preserve the existing checklist formatting.plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/references/security-analysis-with-event-modeling.md-9-9 (1)
9-9:⚠️ Potential issue | 🟡 MinorFix hyphenation in quoted sentence for readability.
Use “time-consuming” instead of “time consuming”.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/references/security-analysis-with-event-modeling.md` at line 9, Update the quoted sentence string that currently reads "With an event model, the solution shows exactly where, and equally importantly, when sensitive data crosses boundaries. With traditional audits, the number of interviews with staff was time consuming and at risk of missing important areas." to use correct hyphenation by replacing "time consuming" with "time-consuming" in the quote; ensure the change appears in the same quoted paragraph text so the sentence reads naturally and retains original punctuation.plugins/trogonstack-eventmodeling/skills/eventmodeling-storyboarding-events/SKILL.md-42-42 (1)
42-42:⚠️ Potential issue | 🟡 MinorAdd language tags to fenced code blocks.
Please label all fenced blocks (
text/markdown) to resolve MD040 warnings.Also applies to: 95-95, 129-129, 162-162, 195-195, 220-220, 258-258, 288-288, 331-331, 361-361, 415-415, 426-426, 437-437
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-storyboarding-events/SKILL.md` at line 42, Several fenced code blocks in SKILL.md are unlabeled (triggering MD040); update each triple-backtick block to include an appropriate language tag (e.g., ```markdown or ```text) so linters can detect the block type. Locate the unlabeled fenced blocks mentioned in the review (occurrences around the shown block plus those at 95,129,162,195,220,258,288,331,361,415,426,437) and add consistent language tags matching the content of each block. Ensure you only change the opening ``` to ```markdown or ```text as appropriate and do not alter the block contents. Run your markdown linter to confirm MD040 warnings are resolved.plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md-39-39 (1)
39-39:⚠️ Potential issue | 🟡 MinorAdd language identifiers for fenced blocks (MD040).
Please annotate these code blocks with
text/markdownfor lint compliance.Also applies to: 58-58, 75-75, 111-111, 133-133, 162-162, 208-208, 232-232, 357-357, 370-370, 383-383
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md` at line 39, The markdown file SKILL.md contains several fenced code blocks missing language identifiers; update every triple-backtick block in this document to include an explicit language tag (use text or markdown as appropriate) so they comply with MD040 linting; search for all ``` blocks in SKILL.md and add the language tokens (e.g., ```text or ```markdown) consistently across the blocks referenced in the review.plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/examples.md-16-16 (1)
16-16:⚠️ Potential issue | 🟡 MinorAnnotate fenced code blocks with language identifiers.
Please add
text/markdownto these fences to clear MD040 warnings.Also applies to: 91-91, 102-102, 114-114, 130-130, 161-161, 181-181, 193-193, 214-214
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/examples.md` at line 16, Several fenced code blocks in examples.md are missing language identifiers and trigger MD040; open the file plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/examples.md and update each triple-backtick fence that currently has no language (the example blocks) to include an appropriate identifier such as text or markdown (e.g., ```text or ```markdown) so each fenced block is annotated; ensure you update all occurrences mentioned in the review (the example fences throughout the document).plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/patterns.md-16-16 (1)
16-16:⚠️ Potential issue | 🟡 MinorAdd language identifiers to fenced code blocks to satisfy MD040.
This file has many unlabeled fences. Please use explicit language tags (for example
text/markdown) consistently to keep markdownlint clean.Also applies to: 79-79, 91-91, 112-112, 124-124, 140-140, 152-152, 172-172, 189-189, 203-203, 223-223, 239-239, 256-256, 270-270, 296-296, 338-338, 354-354, 366-366, 388-388, 401-401
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/patterns.md` at line 16, The fenced code blocks in patterns.md are unlabeled and trigger MD040; update every triple-backtick fence (including the occurrences around lines referenced: 79, 91, 112, 124, 140, 152, 172, 189, 203, 223, 239, 256, 270, 296, 338, 354, 366, 388, 401 and the one shown) by adding an explicit language identifier (for example use "text" or "markdown" as appropriate) after the opening ``` so each fenced block is labeled and markdownlint MD040 is satisfied.plugins/trogonstack-eventmodeling/skills/eventmodeling-applying-conways-law/SKILL.md-48-48 (1)
48-48:⚠️ Potential issue | 🟡 MinorAdd language labels to fenced code blocks.
This resolves the current markdownlint MD040 warnings and keeps doc formatting standards consistent.
Also applies to: 135-135, 149-149, 213-213, 344-344
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-applying-conways-law/SKILL.md` at line 48, Several fenced code blocks in SKILL.md (for example the block following the line "Then: Skip interview, proceed directly to swimlanes" and the blocks around the other noted locations) are missing language identifiers and causing markdownlint MD040 warnings; update each fenced block by adding an appropriate language label (e.g., ```json, ```yaml, ```mermaid, ```text) to the opening fence so the blocks have explicit languages, and apply the same change to the other referenced blocks (around the content at the other noted ranges) to resolve the lint warnings and keep formatting consistent.plugins/trogonstack-eventmodeling/skills/eventmodeling-plotting-events/SKILL.md-44-44 (1)
44-44:⚠️ Potential issue | 🟡 MinorAdd fence language annotations to clear MD040 warnings.
Use
textfor narrative diagrams andmarkdownwhere templates are intended to be copied.Also applies to: 128-128, 150-150, 165-165
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-plotting-events/SKILL.md` at line 44, In SKILL.md there are fenced code blocks missing language hints which trigger MD040; update each empty fence used for narrative diagrams to use the language tag text (e.g., change ``` to ```text) and update fences that contain copy/paste-able templates to use the markdown tag (```markdown), locating the blocks by their surrounding narrative diagram text and template headings and applying the appropriate language annotation to each occurrence.plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md-168-178 (1)
168-178:⚠️ Potential issue | 🟡 MinorAlign examples with the “no generic User” rule.
The template forbids generic “User”, but command examples still use it as Source. Use specific roles (Customer, Seller, Support Agent, etc.) in examples to avoid contradictory guidance.
Proposed fix
- Source: User (Order Entry screen) + Source: Customer (Order Entry screen) - Source: User (Confirmation screen) + Source: Customer (Confirmation screen) - Source: User (Status screen) + Source: Customer (Status screen) -**Source**: User (Order Entry screen) +**Source**: Customer (Order Entry screen)Also applies to: 275-275, 332-332
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md` around lines 168 - 178, Replace the generic "User" source in the command examples with specific roles to follow the "no generic User" rule: update the entries for CreateOrder (Source: User → Source: Customer), ConfirmOrder (Source: User → Source: Customer or Payment Agent as appropriate), and CancelOrder (Source: User → Source: Customer or Support Agent) in SKILL.md, and similarly change the other occurrences reported at the same pattern (around lines noted in the review) so every "Source: User" becomes a concrete role like Customer, Seller, Support Agent, or Payment Agent depending on the command's intent.plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/references/security-analysis-with-event-modeling.md-15-15 (1)
15-15:⚠️ Potential issue | 🟡 MinorSpecify fence languages across unlabeled code blocks.
Please add code fence language tags (
text/markdown) to resolve MD040 warnings.Also applies to: 34-34, 56-56, 87-87, 116-116, 154-154, 168-168, 217-217, 264-264, 338-338, 375-375, 390-390
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/references/security-analysis-with-event-modeling.md` at line 15, Add explicit fence languages to every unlabeled triple-backtick code fence in security-analysis-with-event-modeling.md (replace plain ``` with ```text or ```markdown as appropriate). Locate the code fences that currently have no language and update them consistently (e.g., use ```markdown for prose/MD examples and ```text for plain text snippets) so MD040 warnings are resolved.plugins/trogonstack-eventmodeling/skills/eventmodeling-brainstorming-events/SKILL.md-48-48 (1)
48-48:⚠️ Potential issue | 🟡 MinorUse explicit fence languages for all code blocks.
Please annotate these fences with
text/markdownto satisfy MD040 and keep style consistent with the rest of the plugin docs.Also applies to: 135-135, 149-149, 213-213, 344-344
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-brainstorming-events/SKILL.md` at line 48, Replace the bare triple-backtick code fences in SKILL.md with explicit fenced code blocks annotated with a language (use `text` or `markdown`) for each reported occurrence; specifically update the unannotated fences (the occurrences noted by the reviewer) so each block starts with ```text or ```markdown to satisfy MD040 and match the plugin's doc style.plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/references/security-analysis-with-event-modeling.md-159-159 (1)
159-159:⚠️ Potential issue | 🟡 MinorFill missing sensitivity classification in the matrix row.
PaymentAuthorized | authCode |currently leaves sensitivity blank, which undermines the example and can cause misclassification downstream.Proposed fix
-| PaymentAuthorized | authCode | | Payment stream | Refund processor | Hidden | Encrypted, HSM, Access log | +| PaymentAuthorized | authCode | Highly Sensitive | Payment stream | Refund processor | Hidden | Encrypted, HSM, Access log |🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/references/security-analysis-with-event-modeling.md` at line 159, The matrix row for the event "PaymentAuthorized" with attribute "authCode" is missing its sensitivity classification; update that cell to a proper sensitivity label (e.g., "Confidential" or "Sensitive") so the row becomes "PaymentAuthorized | authCode | Confidential | Payment stream | Refund processor | Hidden | Encrypted, HSM, Access log" and ensure the same label style is used consistently across the matrix entries.plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md-343-343 (1)
343-343:⚠️ Potential issue | 🟡 MinorFix empty symbol placeholders in automation checklist item.
The phrase currently renders as empty parentheses and loses meaning. Replace with explicit labels.
Proposed fix
-- [ ] **Automation marked with gear symbols () to distinguish from user actions ()** +- [ ] **Automation clearly marked (e.g., `[Processor]` vs `[Human Role]`)**🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md` at line 343, The checklist line "- [ ] **Automation marked with gear symbols () to distinguish from user actions ()**" contains empty icon placeholders; update that markdown to include explicit symbols or labels so it renders clearly (for example replace the first empty parentheses with a gear emoji or the word "automation" like "(⚙️ automation)" and the second with a user icon or label like "(👤 user)"); modify the SKILL.md checklist item text (the line containing "Automation marked with gear symbols" and the trailing empty parentheses) to use the chosen visible labels so the meaning is preserved.plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/examples.md-64-64 (1)
64-64:⚠️ Potential issue | 🟡 MinorFix truncated event name.
SellerResponsePub.looks like an accidental truncation; use the full event name for consistency with the rest of the docs.Proposed fix
- Events Produced: SellerResponseSubmitted, SellerResponsePub. + Events Produced: SellerResponseSubmitted, SellerResponsePublished🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/examples.md` at line 64, The "Events Produced" line contains a truncated event name "SellerResponsePub."—replace it with the full event name used elsewhere in the docs (e.g., "SellerResponsePublished" or the exact canonical event name used in this project) so the line reads "Events Produced: SellerResponseSubmitted, <FullSellerResponseEventName>." Update the entry in the examples.md "Events Produced" list to match the canonical event symbol used across the repo (search for occurrences of SellerResponse* to confirm exact spelling) to ensure consistency.plugins/trogonstack-eventmodeling/skills/eventmodeling-designing-event-models/SKILL.md-425-425 (1)
425-425:⚠️ Potential issue | 🟡 MinorFix spelling error: "uncofirmed" → "unconfirmed".
The example text contains a typo that should be corrected for professional documentation.
📝 Proposed fix
-- "Obviously can't ship an uncofirmed order" +- "Obviously can't ship an unconfirmed order"🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-designing-event-models/SKILL.md` at line 425, The sentence string "Obviously can't ship an uncofirmed order" contains a spelling error; update that literal to "Obviously can't ship an unconfirmed order" wherever it appears in SKILL.md (look for the exact quoted text) so the documentation uses the correct word "unconfirmed".plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-outputs/SKILL.md-29-29 (1)
29-29:⚠️ Potential issue | 🟡 MinorRemove extra space after
##in heading.The heading has two spaces after
##instead of one. This violates markdown formatting conventions.📝 Proposed fix
-## CRITICAL: Events vs Read Models +## CRITICAL: Events vs Read Models🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-outputs/SKILL.md` at line 29, The Markdown heading "## CRITICAL: Events vs Read Models" contains two spaces after "##"; edit the SKILL.md content to change the heading to use a single space ("## CRITICAL: Events vs Read Models") so it follows standard Markdown heading formatting and renders correctly.plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-outputs/SKILL.md-86-105 (1)
86-105:⚠️ Potential issue | 🟡 MinorAdd language specifiers to fenced code blocks.
The code blocks showing anti-patterns and correct patterns should specify a language identifier (e.g.,
yaml,json, ortext) for better rendering and syntax highlighting.📝 Proposed fix
- WRONG: Modeling as Event -``` +```yaml ReviewRatingCalculated sellerId: seller-123 averageRating: 4.5 (This recalculates!)And similarly for the CORRECT example:
- CORRECT: Model as Read Model -``` +```yaml SellerRatingView sellerId: seller-123🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-outputs/SKILL.md` around lines 86 - 105, In the SKILL.md examples, the fenced code blocks showing the anti-pattern starting with "ReviewRatingCalculated" and the correct pattern starting with "SellerRatingView" need language specifiers (use yaml) so they render with syntax highlighting; update the opening fences for those blocks from ``` to ```yaml for both the WRONG and CORRECT examples and ensure indentation/contents remain unchanged.
🧹 Nitpick comments (6)
plugins/trogonstack-eventmodeling/skills/eventmodeling-designing-event-models/SKILL.md (3)
84-288: Add language specifiers to workflow code blocks.Multiple code blocks in the workflow section lack language specifiers, reducing readability and preventing syntax highlighting. Consider adding appropriate identifiers (
yaml,text,typescript, etc.) to blocks at lines 84, 137, 181, 219, 254, 269, 322, and 330.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-designing-event-models/SKILL.md` around lines 84 - 288, Several fenced code blocks in the document (e.g., the Stream example "Stream: Order:order-123", the command examples "Command: ConfirmOrder", "ConfirmOrder Command" state builder, "ShipOrder Command", the ReadModel "OrderSummaryView", and the state transition / causality blocks) are missing language specifiers; update each triple-backtick block to include an appropriate language tag (e.g., yaml, text, json, typescript, or plain; choose the best-fit for each block like `yaml` for structured data, `text` for plain prose, `typescript` for interfaces/builders) so that syntax highlighting and readability are enabled for the blocks that show events, command definitions, state builders, read model schemas, and transition diagrams.
381-395: Add language specifiers to pattern code blocks.The Compensation Pattern and Temporal Queries examples use code blocks without language specifiers. Consider adding
textorpseudocodeidentifiers.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-designing-event-models/SKILL.md` around lines 381 - 395, The two fenced code blocks under "Compensation Pattern" (the block showing Command: ProcessPayment ... OrderCancelled) and "Temporal Queries" (the block showing Replay events up to timestamp T ...) lack language specifiers; update each triple-backtick fence to include a language identifier such as text or pseudocode (e.g., ```text or ```pseudocode) so syntax highlighters and renderers treat them as plain/pseudocode content while leaving the block contents unchanged.
36-60: Add language specifier to the architectural example code block.The critical code block contrasting wrong vs correct architectural patterns should have a language specifier (e.g.,
typescript,text, orpseudocode) for better rendering.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-designing-event-models/SKILL.md` around lines 36 - 60, The code block showing WRONG vs CORRECT event modeling lacks a language specifier which affects syntax highlighting; update the fenced code block around the ReviewAggregate / PublishReviewState examples to include an appropriate language tag (e.g., "text" or "typescript") so it renders correctly. Locate the block containing ReviewAggregate, handlePublishReview, PublishReviewState, EditReviewState, DeleteReviewState and ReviewReadModel and add the language marker after the opening triple backticks (for example ```text or ```typescript) to the exact fenced block.plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-outputs/SKILL.md (3)
319-340: Add language specifiers to nested code blocks in the output template.The example output template contains nested code blocks (lines 319 and 340) that lack language specifiers. These should use
jsonortypescriptfor the data structure examples.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-outputs/SKILL.md` around lines 319 - 340, The nested code blocks showing the order object schema (fields like orderId, customerId, status, items, total, shippingAddress, createdAt, confirmedAt, etc.) lack language specifiers; update those fenced code blocks to use an appropriate language tag (e.g., ```json or ```typescript) so syntax highlighting is applied for the data-structure examples in SKILL.md.
427-452: Add language specifiers to pattern example code blocks.The four common pattern examples (Status View, List View, Timeline View, Processor Decision) use code blocks without language specifiers. Consider adding
textoryamlidentifiers.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-outputs/SKILL.md` around lines 427 - 452, The code blocks under the four pattern examples in SKILL.md (Status View Pattern, List View Pattern, Timeline View Pattern, Processor Decision Pattern) lack language specifiers; update each triple-backtick block to include a language tag (e.g., ```text or ```yaml) so syntax highlighters render them consistently—specifically modify the three-line blocks showing "Events: ..., ReadModel: ..., Displayed/Used: ..." for Status View, List View, Timeline View and Processor Decision to begin with ```text (or another chosen language) and end with ```.
121-284: Add language specifiers to all fenced code blocks in Workflow section.Multiple code blocks throughout the workflow lack language specifiers, which reduces clarity and prevents proper syntax highlighting. Consider adding appropriate identifiers (
yaml,text, ormarkdowndepending on content).Examples include blocks at lines 121, 144, 164, 201, 241, and 261.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-outputs/SKILL.md` around lines 121 - 284, Several fenced code blocks in the Workflow/skills content (e.g., the "Screen: Order Status View" block, "ReadModel: OrderStatusView", the "Event: OrderCreated"/"Event: OrderConfirmed"/"Event: PaymentAuthorized"/"Event: OrderShipped" blocks, the "ReadModel Catalog: Order System" section, and the "Processor: Inventory System"/"Processor: Fulfillment System"/"Processor: Notification System" blocks) are missing language specifiers; update each triple-backtick fence to include an appropriate language token (for example use "text" or "markdown" for plain descriptions, "yaml" if the block is structured/field-like, or "json" where appropriate) so syntax highlighting and clarity improve across the Workflow section.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-elaborating-scenarios/SKILL.md`:
- Around line 404-531: The outer Markdown code fence in SKILL.md that wraps the
scenarios uses triple backticks (```markdown) while the inner examples also use
triple backtick gherkin blocks (```gherkin), causing premature closure; to fix,
replace the outer opening and closing fences with four backticks (````markdown
... ````) so the inner ```gherkin blocks remain valid, or alternatively convert
the inner ```gherkin blocks to indented code blocks; look for the outer fence
surrounding the scenarios and the inner ```gherkin blocks to update.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/SKILL.md`:
- Around line 67-73: The formula block titled "Estimated Stream Length" mixes
unit bases; make the units explicit and consistent by specifying whether "Events
Per Aggregate Instance" is per-instance-per-year or total-per-instance, define
"Lifetime of Instance (years)" as years, and state "Annual Growth Factor" as a
dimensionless year-over-year multiplier; then update the surrounding examples
(lines referencing the formula) to use the same time basis (convert monthly
rates to per-year or vice versa) and annotate each term with its unit (e.g.,
events/instance/year or events/instance) so all calculations and snapshotting
recommendations use compatible units.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/references/project-planning-with-event-modeling.md`:
- Line 125: The document mixes sprint length assumptions: update the estimate
line that reads "Estimate: 9 ÷ 3 = 3 sprints = ~9 weeks" and the section that
maps "1 sprint = 4 weeks" so they use the same sprint duration; choose one
canonical sprint length (e.g., 4 weeks or 3 weeks), recompute all derived week
totals and textual examples accordingly (including the "Estimate: 9 ÷ 3 ..."
calculation and the block around lines 154-157), and ensure any other mentions
of sprint-to-weeks conversions in the file are updated to match the chosen
standard.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/examples.md`:
- Around line 166-167: The dependency matrix contradicts the earlier slice
definitions: the matrix row for "Responses" (and symmetrical "Ratings") lists a
dependency on "Moderation" while the prose states Slice 3 is parallel with Slice
2. Update the document so the dependency model is consistent—either remove the
"← Depends" from the "Responses" (and "Ratings") columns that reference
"Moderation" in the matrix to mark them independent, or change the slice
definition that declares Slice 3 parallel with Slice 2 to indicate a dependency;
ensure the unique symbols "Responses", "Ratings", "Moderation", "Slice 3", and
"Slice 2" are updated together so both the matrix and slice descriptions match.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/SKILL.md`:
- Around line 99-112: The orchestrator flow never invokes the documented skill
"eventmodeling-slicing-event-models", so add an explicit handoff in the
orchestrator workflow: locate the orchestrator function or class that finishes
the modeling/validation step (e.g., orchestrator.run,
Orchestrator.handleValidationOutcome, or WorkflowEngine.routeAfterValidation)
and insert a transition that calls or queues the
"eventmodeling-slicing-event-models" skill (preserving existing validation
success/failure branching), update any routing/skill registry to include the
skill name "eventmodeling-slicing-event-models", and ensure the step appears in
the user-facing flow so the skill becomes reachable after model validation.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-translating-external-events/SKILL.md`:
- Around line 249-299: The outer Markdown fenced code block starting at the top
of the template (the ```markdown fence around the whole template) is being
closed prematurely by the inner triple-backtick blocks under "Technical
Representation" and "Translation Logic"; to fix, replace the outer fence with a
longer fence (e.g., ````markdown) or convert the inner triple-backtick examples
(the JSON under "Technical Representation" and the numbered block under
"Translation Logic") to indented code blocks (4-space indent) so the inner
fences do not terminate the outer block and the template renders correctly.
---
Minor comments:
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-applying-conways-law/SKILL.md`:
- Line 48: Several fenced code blocks in SKILL.md (for example the block
following the line "Then: Skip interview, proceed directly to swimlanes" and the
blocks around the other noted locations) are missing language identifiers and
causing markdownlint MD040 warnings; update each fenced block by adding an
appropriate language label (e.g., ```json, ```yaml, ```mermaid, ```text) to the
opening fence so the blocks have explicit languages, and apply the same change
to the other referenced blocks (around the content at the other noted ranges) to
resolve the lint warnings and keep formatting consistent.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-brainstorming-events/SKILL.md`:
- Line 48: Replace the bare triple-backtick code fences in SKILL.md with
explicit fenced code blocks annotated with a language (use `text` or `markdown`)
for each reported occurrence; specifically update the unannotated fences (the
occurrences noted by the reviewer) so each block starts with ```text or
```markdown to satisfy MD040 and match the plugin's doc style.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/references/security-analysis-with-event-modeling.md`:
- Line 9: Update the quoted sentence string that currently reads "With an event
model, the solution shows exactly where, and equally importantly, when sensitive
data crosses boundaries. With traditional audits, the number of interviews with
staff was time consuming and at risk of missing important areas." to use correct
hyphenation by replacing "time consuming" with "time-consuming" in the quote;
ensure the change appears in the same quoted paragraph text so the sentence
reads naturally and retains original punctuation.
- Line 15: Add explicit fence languages to every unlabeled triple-backtick code
fence in security-analysis-with-event-modeling.md (replace plain ``` with
```text or ```markdown as appropriate). Locate the code fences that currently
have no language and update them consistently (e.g., use ```markdown for
prose/MD examples and ```text for plain text snippets) so MD040 warnings are
resolved.
- Line 159: The matrix row for the event "PaymentAuthorized" with attribute
"authCode" is missing its sensitivity classification; update that cell to a
proper sensitivity label (e.g., "Confidential" or "Sensitive") so the row
becomes "PaymentAuthorized | authCode | Confidential | Payment stream | Refund
processor | Hidden | Encrypted, HSM, Access log" and ensure the same label style
is used consistently across the matrix entries.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-designing-event-models/SKILL.md`:
- Line 425: The sentence string "Obviously can't ship an uncofirmed order"
contains a spelling error; update that literal to "Obviously can't ship an
unconfirmed order" wherever it appears in SKILL.md (look for the exact quoted
text) so the documentation uses the correct word "unconfirmed".
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md`:
- Line 39: The markdown file SKILL.md contains several fenced code blocks
missing language identifiers; update every triple-backtick block in this
document to include an explicit language tag (use text or markdown as
appropriate) so they comply with MD040 linting; search for all ``` blocks in
SKILL.md and add the language tokens (e.g., ```text or ```markdown) consistently
across the blocks referenced in the review.
- Around line 168-178: Replace the generic "User" source in the command examples
with specific roles to follow the "no generic User" rule: update the entries for
CreateOrder (Source: User → Source: Customer), ConfirmOrder (Source: User →
Source: Customer or Payment Agent as appropriate), and CancelOrder (Source: User
→ Source: Customer or Support Agent) in SKILL.md, and similarly change the other
occurrences reported at the same pattern (around lines noted in the review) so
every "Source: User" becomes a concrete role like Customer, Seller, Support
Agent, or Payment Agent depending on the command's intent.
- Line 343: The checklist line "- [ ] **Automation marked with gear symbols ()
to distinguish from user actions ()**" contains empty icon placeholders; update
that markdown to include explicit symbols or labels so it renders clearly (for
example replace the first empty parentheses with a gear emoji or the word
"automation" like "(⚙️ automation)" and the second with a user icon or label
like "(👤 user)"); modify the SKILL.md checklist item text (the line containing
"Automation marked with gear symbols" and the trailing empty parentheses) to use
the chosen visible labels so the meaning is preserved.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-outputs/SKILL.md`:
- Line 29: The Markdown heading "## CRITICAL: Events vs Read Models" contains
two spaces after "##"; edit the SKILL.md content to change the heading to use a
single space ("## CRITICAL: Events vs Read Models") so it follows standard
Markdown heading formatting and renders correctly.
- Around line 86-105: In the SKILL.md examples, the fenced code blocks showing
the anti-pattern starting with "ReviewRatingCalculated" and the correct pattern
starting with "SellerRatingView" need language specifiers (use yaml) so they
render with syntax highlighting; update the opening fences for those blocks from
``` to ```yaml for both the WRONG and CORRECT examples and ensure
indentation/contents remain unchanged.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/domain-patterns.md`:
- Line 14: Update the fenced code blocks in domain-patterns.md to include a
language identifier (e.g., add ```text instead of just ```) for each fenced
block referenced (the blocks at the positions noted in the review: lines 14, 24,
34, 48, 59, 69, 84, 94, 104, and 122) so they comply with the linter; simply
edit each opening triple-backtick to include "text" (```text) and leave the
block contents unchanged.
- Line 132: Fix the typo in the checklist question by replacing the misspelled
token "snaphotting" with the correct "snapshotting" in the checklist line
containing "[ ] Is the problem snaphotting will solve?" so the line reads "[ ]
Is the problem snapshotting will solve?" and preserve the existing checklist
formatting.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/patterns.md`:
- Line 16: Update all fenced code blocks opened with ``` to include a language
identifier to satisfy markdownlint and improve rendering: replace the bare
fences at the reported locations (all occurrences where a block starts with ```
on lines like 16, 44, 82, 119, 158, 196, 252, 289, 296, 304, 316, 325) with
```text for plain text blocks or ```yaml where the content is YAML; ensure each
opening fence matches its closing ``` so rendering and linting pass.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/snapshotting.md`:
- Line 48: The fenced code block opened immediately after the heading
"**Question 2: What's your read latency requirement?**" is missing a language
specifier; update the opening fence from ``` to ```text so the block is marked
as text (e.g., change the triple backticks that start that code block to
```text) to satisfy docs lint rules.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/SKILL.md`:
- Line 68: The markdown in SKILL.md contains three fenced code blocks that are
missing language identifiers (the blocks around the examples at the three spots
called out in the review); to satisfy markdownlint, open each triple-backtick
fence and add a language token (use "text") so they read ```text, ensuring all
three blocks are updated consistently to remove the lint warnings.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/references/project-planning-with-event-modeling.md`:
- Line 11: Fix markdownlint MD040 and MD019 in
project-planning-with-event-modeling.md by adding language identifiers to all
fenced code blocks (e.g., change ``` to ```text or appropriate language) and
removing the extra double space after "###" headings so they use single space
(e.g., "### Heading" not "### Heading"); apply these changes to the mentioned
code fences and headings (lines referenced: 11, 35, 57, 84, 106, 146, 179, 193,
225, 244, 265, 267, 273, 275, 281, 283, 296, 325) and verify markdownlint no
longer reports MD040/MD019.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-plotting-events/SKILL.md`:
- Line 44: In SKILL.md there are fenced code blocks missing language hints which
trigger MD040; update each empty fence used for narrative diagrams to use the
language tag text (e.g., change ``` to ```text) and update fences that contain
copy/paste-able templates to use the markdown tag (```markdown), locating the
blocks by their surrounding narrative diagram text and template headings and
applying the appropriate language annotation to each occurrence.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/examples.md`:
- Line 16: Several fenced code blocks in examples.md are missing language
identifiers and trigger MD040; open the file
plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/examples.md
and update each triple-backtick fence that currently has no language (the
example blocks) to include an appropriate identifier such as text or markdown
(e.g., ```text or ```markdown) so each fenced block is annotated; ensure you
update all occurrences mentioned in the review (the example fences throughout
the document).
- Line 64: The "Events Produced" line contains a truncated event name
"SellerResponsePub."—replace it with the full event name used elsewhere in the
docs (e.g., "SellerResponsePublished" or the exact canonical event name used in
this project) so the line reads "Events Produced: SellerResponseSubmitted,
<FullSellerResponseEventName>." Update the entry in the examples.md "Events
Produced" list to match the canonical event symbol used across the repo (search
for occurrences of SellerResponse* to confirm exact spelling) to ensure
consistency.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/patterns.md`:
- Line 16: The fenced code blocks in patterns.md are unlabeled and trigger
MD040; update every triple-backtick fence (including the occurrences around
lines referenced: 79, 91, 112, 124, 140, 152, 172, 189, 203, 223, 239, 256, 270,
296, 338, 354, 366, 388, 401 and the one shown) by adding an explicit language
identifier (for example use "text" or "markdown" as appropriate) after the
opening ``` so each fenced block is labeled and markdownlint MD040 is satisfied.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-storyboarding-events/SKILL.md`:
- Line 42: Several fenced code blocks in SKILL.md are unlabeled (triggering
MD040); update each triple-backtick block to include an appropriate language tag
(e.g., ```markdown or ```text) so linters can detect the block type. Locate the
unlabeled fenced blocks mentioned in the review (occurrences around the shown
block plus those at 95,129,162,195,220,258,288,331,361,415,426,437) and add
consistent language tags matching the content of each block. Ensure you only
change the opening ``` to ```markdown or ```text as appropriate and do not alter
the block contents. Run your markdown linter to confirm MD040 warnings are
resolved.
---
Duplicate comments:
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/references/project-planning-with-event-modeling.md`:
- Around line 162-163: The document shows contradictory totals: the line "TOTAL
13 4 sprints ~22 weeks" (and the other occurrence at 171–173) mixes a 13 and
~22 in a way that reverses the intended conclusion; update these two places so
the "without parallelization" case reflects the longer duration (~22 weeks) and
the "with parallelization" case reflects the shorter duration (~13 weeks) —
i.e., swap/correct the numeric totals so the parallelized delivery is ~13 weeks
and the non-parallelized delivery is ~22 weeks consistently.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-storyboarding-events/SKILL.md`:
- Around line 404-406: The checklist line currently contains the heading
appended to it; locate the line containing "- [ ] **System boundaries visible
through swimlane organization** ## Key Principles" and split it into two
separate lines so the checklist stays on its own and "## Key Principles" becomes
a standalone heading on the next line, preserving surrounding formatting and
spacing.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models-checklist/SKILL.md`:
- Around line 4-5: The SKILL.md Claim "23 checks" is inconsistent with the
actual checklist items (16); update the document so the claimed number matches
the defined checks: either add the missing 7 checks to the checklist or change
every occurrence of "23 checks"/"23" to the correct total, and ensure the
scoring/completion criteria and any summary sections (the lead sentence
"Validate event-sourced CQRS models...", the checklist summary lines that repeat
the count, and the scoring/completion paragraphs) reflect the same, reconciled
count so totals and scoring logic are consistent across the file.
---
Nitpick comments:
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-designing-event-models/SKILL.md`:
- Around line 84-288: Several fenced code blocks in the document (e.g., the
Stream example "Stream: Order:order-123", the command examples "Command:
ConfirmOrder", "ConfirmOrder Command" state builder, "ShipOrder Command", the
ReadModel "OrderSummaryView", and the state transition / causality blocks) are
missing language specifiers; update each triple-backtick block to include an
appropriate language tag (e.g., yaml, text, json, typescript, or plain; choose
the best-fit for each block like `yaml` for structured data, `text` for plain
prose, `typescript` for interfaces/builders) so that syntax highlighting and
readability are enabled for the blocks that show events, command definitions,
state builders, read model schemas, and transition diagrams.
- Around line 381-395: The two fenced code blocks under "Compensation Pattern"
(the block showing Command: ProcessPayment ... OrderCancelled) and "Temporal
Queries" (the block showing Replay events up to timestamp T ...) lack language
specifiers; update each triple-backtick fence to include a language identifier
such as text or pseudocode (e.g., ```text or ```pseudocode) so syntax
highlighters and renderers treat them as plain/pseudocode content while leaving
the block contents unchanged.
- Around line 36-60: The code block showing WRONG vs CORRECT event modeling
lacks a language specifier which affects syntax highlighting; update the fenced
code block around the ReviewAggregate / PublishReviewState examples to include
an appropriate language tag (e.g., "text" or "typescript") so it renders
correctly. Locate the block containing ReviewAggregate, handlePublishReview,
PublishReviewState, EditReviewState, DeleteReviewState and ReviewReadModel and
add the language marker after the opening triple backticks (for example ```text
or ```typescript) to the exact fenced block.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-outputs/SKILL.md`:
- Around line 319-340: The nested code blocks showing the order object schema
(fields like orderId, customerId, status, items, total, shippingAddress,
createdAt, confirmedAt, etc.) lack language specifiers; update those fenced code
blocks to use an appropriate language tag (e.g., ```json or ```typescript) so
syntax highlighting is applied for the data-structure examples in SKILL.md.
- Around line 427-452: The code blocks under the four pattern examples in
SKILL.md (Status View Pattern, List View Pattern, Timeline View Pattern,
Processor Decision Pattern) lack language specifiers; update each
triple-backtick block to include a language tag (e.g., ```text or ```yaml) so
syntax highlighters render them consistently—specifically modify the three-line
blocks showing "Events: ..., ReadModel: ..., Displayed/Used: ..." for Status
View, List View, Timeline View and Processor Decision to begin with ```text (or
another chosen language) and end with ```.
- Around line 121-284: Several fenced code blocks in the Workflow/skills content
(e.g., the "Screen: Order Status View" block, "ReadModel: OrderStatusView", the
"Event: OrderCreated"/"Event: OrderConfirmed"/"Event: PaymentAuthorized"/"Event:
OrderShipped" blocks, the "ReadModel Catalog: Order System" section, and the
"Processor: Inventory System"/"Processor: Fulfillment System"/"Processor:
Notification System" blocks) are missing language specifiers; update each
triple-backtick fence to include an appropriate language token (for example use
"text" or "markdown" for plain descriptions, "yaml" if the block is
structured/field-like, or "json" where appropriate) so syntax highlighting and
clarity improve across the Workflow section.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
plugins/trogonstack-eventmodeling/skills/eventmodeling-elaborating-scenarios/SKILL.md
Outdated
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/SKILL.md
Show resolved
Hide resolved
...ventmodeling-orchestrating-event-modeling/references/project-planning-with-event-modeling.md
Outdated
Show resolved
Hide resolved
...s/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/examples.md
Outdated
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/SKILL.md
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-translating-external-events/SKILL.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 758bdb5. Configure here.
plugins/trogonstack-eventmodeling/skills/eventmodeling-applying-conways-law/SKILL.md
Show resolved
Hide resolved
There was a problem hiding this comment.
Actionable comments posted: 9
♻️ Duplicate comments (8)
plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/SKILL.md (1)
123-139:⚠️ Potential issue | 🟠 MajorClarify formula units and fix inconsistent examples.
The formula at lines 123-129 and examples at lines 133-139 still mix incompatible unit bases, which can lead to incorrect stream-length estimates and wrong snapshotting decisions. This issue was flagged in a previous review but remains unresolved.
Problems:
- Line 133: "8 avg events × 1.5 year" uses no time basis for the 8 events and yields an impossible range (8-16 ≠ 8 × 1.5)
- Line 135: Correctly uses "per year" basis ✓
- Line 137: "100+ per order" is ambiguous—does this mean per-order lifetime or per-order per-year?
- Line 139: Uses monthly rate without converting to annual in the calculation display
📐 Proposed corrections
Step 1: Clarify the formula by making units explicit:
**Formula**: -``` -Estimated Stream Length = -Events Per Aggregate Instance - × Lifetime of Instance (years) - × Annual Growth Factor -``` +``` +Estimated Stream Length = + (Events per Instance per Year) + × Lifetime of Instance (years) + × Growth Multiplier (year-over-year) + +OR for known totals: + (Total Events per Instance Lifetime) + × Growth Multiplier +``` **Step 2**: Fix examples to use consistent units: ```diff **Quick Examples**: -**E-commerce Order**: 8 avg events × 1.5 year lifetime = 8-16 events → NOT NEEDED +**E-commerce Order**: ~8 events per order lifetime × 1.0 growth = 8-12 events → NOT NEEDED -**Banking Account**: 100-200 per year × 10 years = 1000-2000 events → CONSIDER AT 1000+ +**Banking Account**: 100-200 events/year × 10 years × 1.0 growth = 1000-2000 events → CONSIDER AT 1000+ -**Order Processing**: 100+ per order × 5 years = 300-500+ events → PROBABLY NEEDED +**Order Processing**: 100 events/year × 5 years × 1.0 growth = 500+ events → PROBABLY NEEDED -**SaaS User**: 1-5 per month × 5 years = 60-300 events → RARELY NEEDED +**SaaS User**: (1-5 events/month × 12) × 5 years × 1.0 growth = 60-300 events → RARELY NEEDED🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/SKILL.md` around lines 123 - 139, The formula and examples in the "Estimated Stream Length" section mix incompatible time bases; update the formula to explicitly state two variants—(Events per instance per year) × (Lifetime in years) × (Growth multiplier) and alternatively (Total events per instance lifetime) × (Growth multiplier)—and then revise each example to use one consistent basis: for "E-commerce Order" state either "8 events total per order × 1.5 years lifetime = 8 total events" or convert to an annual rate before multiplying; for "Banking Account" keep "100–200 per year × 10 years = 1000–2000" as is; for "Order Processing" clarify whether "100+ per order" means per-year or total (if total, present as total events × growth; if per-year, multiply by lifetime); for "SaaS User" convert "1–5 per month" to annual (12–60 per year) before multiplying by 5 years to show 60–300 events, and ensure every example labels the units used (per year or total).plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/examples.md (1)
166-167:⚠️ Potential issue | 🟠 MajorResolve dependency matrix contradiction with slice definitions.
The dependency matrix at line 166 shows
Responsesdepends onModeration, but the earlier slice definition at lines 48-50 explicitly states Slice 2 (Moderation) and Slice 3 (Responses) "Can Run Parallel" (independent). Additionally, line 63 shows Slice 3 only consumesReviewPublishedfrom Slice 1, not any events from Slice 2.Proposed fix (if Slice 3 is truly independent of Slice 2)
-Responses | ← Depends | ← Depends | (self) | - | +Responses | ← Depends | - | (self) | - |And symmetrically for Ratings if it also doesn't depend on Moderation.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/examples.md` around lines 166 - 167, The dependency matrix contradicts the slice definitions: Slice 2 (Moderation) and Slice 3 (Responses) are declared "Can Run Parallel" and Slice 3 only consumes ReviewPublished from Slice 1, so update the matrix rows/columns for Responses (and symmetrically Ratings if applicable) to show no dependency on Moderation (replace "← Depends" with "-" or "(self)" as appropriate); alternatively, if Responses actually depends on Moderation, update the Slice 2/3 descriptions and the consumed events list for Slice 3 to include the relevant Moderation events so the matrix and slice definitions match (refer to the symbols Responses, Ratings, Slice 2 (Moderation), and Slice 3 (Responses) when making the change).plugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models-checklist/SKILL.md (1)
4-4:⚠️ Potential issue | 🟠 Major"23 checks" claim does not match the enumerated checks.
The document repeatedly claims "23 checks" (lines 4, 15, 26, 211, 316), but the enumerated validation phases only define 16 checks:
- Phase 1: 3 checks
- Phase 2: 3 checks
- Phase 3: 2 checks
- Phase 4: 2 checks
- Phase 5: 1 check
- Phase 6: 1 check
- Phase 7: 1 check
- Final Questions: 3 checks
- Total: 16 checks
Either add 7 missing checks or update all "23 checks" references to "16 checks" and adjust pass/fail criteria accordingly.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models-checklist/SKILL.md` at line 4, The document's repeated "23 checks" claim is incorrect because the enumerated validation phases (Phase 1..7 and Final Questions) only define 16 checks total; update every occurrence of the phrase "23 checks" in SKILL.md (title/intro/body where "23 checks" appears) to "16 checks" and revise any pass/fail criteria, summary statistics, or scoring logic that reference 23 to use 16 instead so counts and thresholds remain consistent with the listed phases (Phase 1:3, Phase 2:3, Phase 3:2, Phase 4:2, Phase 5:1, Phase 6:1, Phase 7:1, Final Questions:3).plugins/trogonstack-eventmodeling/skills/eventmodeling-translating-external-events/SKILL.md (1)
307-407:⚠️ Potential issue | 🟠 MajorOutput template fence nesting breaks markdown rendering.
The outer fence at line 307 (
\``markdown`) is terminated prematurely by the inner triple-backtick fences at lines 330 and 351. Standard Markdown parsers will close the outer block at the first inner fence, breaking the template display.🔧 Proposed fix options
Option 1: Use four backticks for the outer fence:
-```markdown +````markdown # External Event Translation: [Domain Name] ... -``` +````Option 2: Indent inner code examples by 4 spaces so they're rendered as indented code blocks rather than fenced blocks:
**Technical Representation**: -```json -{ - "field1": "value", - "field2": "value" -} -``` + { + "field1": "value", + "field2": "value" + }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-translating-external-events/SKILL.md` around lines 307 - 407, The top-level fenced block beginning with ```markdown (the SKILL.md External Event Translation template) is closed prematurely by inner fenced blocks (the ```json example under "Technical Representation" and the triple-backtick block under "Translation Logic"); fix by replacing the outer fence with a four-backtick fence (````markdown ... ````) or alternatively convert the inner fenced examples to indented code blocks so the outer ```markdown remains intact—update the outer fence token around the "External Event Translation: [Domain Name]" section or change the inner "```json" and the inner triple-backtick in "Translation Logic" to indented blocks to prevent early termination.plugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/references/project-planning-with-event-modeling.md (2)
171-173:⚠️ Potential issue | 🟠 MajorResolve contradictory planning numbers in the comparison.
The parallelized result shows "~22 weeks" while non-parallelized shows "13 weeks", which inverts the intended conclusion that parallelization reduces time. Based on the table showing 13 total steps at 3 steps/sprint velocity, the math should show parallelization delivers faster, not slower.
Example corrected arithmetic
With 3 teams working in parallel on independent steps:
- 13 steps ÷ (3 teams × 3 steps/sprint) ≈ 1.4 sprints ≈ 6 weeks
Without parallelization (1 team):
- 13 steps ÷ 3 steps/sprint ≈ 4.3 sprints ≈ 17 weeks
-Result: All work done in ~22 weeks with proper parallelization -Without parallelization: 13 weeks × 1 team = 13 weeks (but no parallelization possible with tight coupling) +Result: All work done in ~6 weeks with proper parallelization (3 teams) +Without parallelization: ~17 weeks with 1 team (sequential delivery)🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/references/project-planning-with-event-modeling.md` around lines 171 - 173, The summary line "Result: All work done in ~22 weeks with proper parallelization" contradicts the arithmetic and should be corrected to reflect the parallelized calculation: compute 13 steps ÷ (3 teams × 3 steps/sprint) ≈ 1.44 sprints ≈ ~6 weeks and the non-parallelized case as 13 steps ÷ 3 steps/sprint ≈ 4.33 sprints ≈ ~17 weeks; update the "Result" sentence and any adjacent explanatory text in project-planning-with-event-modeling.md to show these corrected week estimates and ensure they match the table's 13 steps and 3 steps/sprint assumptions.
125-125:⚠️ Potential issue | 🟠 MajorUnify sprint duration assumptions before using them in estimates.
Line 125 treats 3 sprints as ~9 weeks (implying 3-week sprints), while the table at lines 154-157 maps each sprint to a 4-week range (e.g., "Week 1-4"). This inconsistency makes the planning guidance unreliable.
Suggested correction pattern
Either standardize on 3-week sprints:
-Estimate: 9 ÷ 3 = 3 sprints = ~9 weeks +Assuming 1 sprint = 3 weeks: +Estimate: 9 ÷ 3 = 3 sprints = ~9 weeks- Core Order Flow 3 1 sprint Week 1-4 + Core Order Flow 3 1 sprint Week 1-3Or standardize on 4-week sprints and update Line 125:
-Estimate: 9 ÷ 3 = 3 sprints = ~9 weeks +Assuming 1 sprint = 4 weeks: +Estimate: 9 ÷ 3 = 3 sprints = ~12 weeks🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/references/project-planning-with-event-modeling.md` at line 125, The document has inconsistent sprint lengths: the phrase "Estimate: 9 ÷ 3 = 3 sprints = ~9 weeks" assumes 3-week sprints while the sprint mapping table ("Week 1-4", etc.) uses 4-week sprints; choose one standard and make both places match — either change the estimate text to use 4-week sprints (e.g., "Estimate: 9 ÷ 4 = 2.25 ≈ 3 sprints = ~12 weeks" or "Estimate: 9 ÷ 4 ≈ 2.25 sprints (~9 weeks of effort across 3 sprints if you keep 4-week sprints)") or update the table entries ("Week 1-3", "Week 4-6", "Week 7-9") to reflect 3-week sprints; update the specific strings "Estimate: 9 ÷ 3 = 3 sprints = ~9 weeks" and the sprint-range rows ("Week 1-4", etc.) so they consistently reflect the chosen sprint duration.plugins/trogonstack-eventmodeling/skills/eventmodeling-storyboarding-events/SKILL.md (1)
404-406:⚠️ Potential issue | 🔴 CriticalSplit checklist item and heading onto separate lines.
Line 404 still merges a checklist item with
## Key Principles, which breaks markdown structure/rendering.Minimal fix
-- [ ] **System boundaries visible through swimlane organization** ## Key Principles +- [ ] **System boundaries visible through swimlane organization** + +## Key Principles🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-storyboarding-events/SKILL.md` around lines 404 - 406, The markdown line currently combines the checklist item "[ ] **System boundaries visible through swimlane organization**" and the heading "## Key Principles" on one line; split them so the checklist item is its own line and the "## Key Principles" heading is on the following line by moving "## Key Principles" to a new line (ensure a blank line between list items and the heading if needed) so the markdown renders correctly.plugins/trogonstack-eventmodeling/skills/eventmodeling-elaborating-scenarios/SKILL.md (1)
404-530:⚠️ Potential issue | 🟠 MajorOuter/inner code fences are still invalidly nested.
The outer
```markdownfence encloses inner```gherkinfences with the same backtick length, so parsing breaks.Use a 4-backtick outer fence
-```markdown +````markdown # Scenarios: [Domain Name] ... -``` +````🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-elaborating-scenarios/SKILL.md` around lines 404 - 530, The Markdown contains nested triple-backtick fences (outer "```markdown" and inner "```gherkin") which breaks parsing; update the outer fence to a 4-backtick fence (e.g., "````markdown" ... "````") or change the inner Gherkin fences to a different fence style so they no longer use the same backtick length—apply this around the Scenarios block containing "Command: CreateOrder" / "ConfirmOrder" and the inner "```gherkin" examples so the outer and inner fences are distinct and the file parses correctly.
🧹 Nitpick comments (3)
plugins/trogonstack-eventmodeling/skills/eventmodeling-integrating-legacy-systems/SKILL.md (1)
164-165: Make Interview Trail update output explicit to avoid inconsistent artifacts.“Update Interview Trail” is directionally correct, but this skill should include the exact row shape to append/update so it stays consistent with orchestration outputs.
Suggested addition
Update Interview Trail with integration-specific findings. +Use this row format in `.trogonai/interviews/[project-name]/EVENTMODELING.md`: +`| Legacy Integration | eventmodeling-integrating-legacy-systems | Done/Blocked | Freeze status, extraction method, recommendation |`🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-integrating-legacy-systems/SKILL.md` around lines 164 - 165, The "Update Interview Trail" step is vague—explicitly define the exact row shape that should be appended/updated so outputs match orchestration artifacts: in SKILL.md update the "Update Interview Trail" section to state the precise field names, types and required/optional flags (e.g., interview_id, timestamp, actor, action, payload) and include a concrete example row/JSON object and a brief note that the orchestration expects this shape; ensure any references to "Interview Trail" and the orchestration outputs mention this schema and that implementers must adhere to it for consistent artifacts.plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/patterns.md (1)
36-36: Inconsistent heading format in template.Line 36 uses
[COMMANDHANDLER]STATES INVOLVED:with unconventional bracket notation and run-together words. Consider eitherCOMMAND HANDLER STATES INVOLVED:orStates Involved:for consistency with the other template sections.♻️ Proposed consistency fix
-[COMMANDHANDLER]STATES INVOLVED: +COMMAND HANDLER STATES INVOLVED: - [CommandHandler]State class: Which handler owns it, how it's reconstructed🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/patterns.md` at line 36, Change the inconsistent heading "[COMMANDHANDLER]STATES INVOLVED:" in patterns.md to match the other template headings; replace the bracketed/run-together form (the exact token "[COMMANDHANDLER]STATES INVOLVED:") with a consistent heading such as "COMMAND HANDLER STATES INVOLVED:" or simply "States Involved:" so it follows the same capitalization and spacing style as other sections.plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md (1)
35-35: Add language tags to all fenced code blocks.These fences are missing language identifiers and are triggering markdownlint MD040. Please annotate each block (for example:
text,markdown) to keep docs lint-clean and consistent.Proposed pattern
-``` +```text If user has provided: - UI actions already listed per storyboard screen ... -``` +```Apply this pattern to all flagged fenced blocks.
Also applies to: 92-92, 111-111, 128-128, 164-164, 186-186, 215-215, 261-261, 285-285, 410-410, 423-423, 436-436
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md` at line 35, Multiple fenced code blocks in SKILL.md are missing language identifiers and trigger markdownlint MD040; update each triple-backtick fence for the flagged blocks by adding an appropriate language tag (e.g., ```text or ```markdown) immediately after the opening ``` so the examples and snippets are lint-clean—apply this to every fenced block referenced (the ones at the reported positions) and ensure the closing ``` remains unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-brainstorming-events/SKILL.md`:
- Around line 48-57: The markdown contains multiple untyped fenced code blocks
(for example the decision-rule block starting "If user has provided:" shown in
the diff and the other blocks at ranges 77-107 and 288-335) which trigger MD040;
add appropriate language/info tags to each fenced block (e.g., ```text or
```yaml depending on content) so the linter recognizes them, ensuring every
triple-backtick fence is converted from ``` to ```text (or another suitable tag)
throughout SKILL.md.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-designing-event-models/SKILL.md`:
- Around line 480-481: Replace the misspelled word in the business rule example
string "Obviously can't ship an uncofirmed order" by changing "uncofirmed" to
"unconfirmed" so the text reads "Obviously can't ship an unconfirmed order";
update the exact string in SKILL.md (search for the quoted line) and leave the
adjacent "ShipOrder validation: requires status='Confirmed' with paymentId" line
unchanged.
- Around line 37-47: The fenced code blocks in SKILL.md (e.g., the block showing
the "If user has provided..." decision logic) are missing language tags and
trigger markdownlint MD040; update each untyped triple-backtick fence (notably
the blocks around lines 37-47, 91-115, and 139-160) to include an appropriate
language identifier such as "text" or "bash" (e.g., change ``` to ```text) so
all fenced code blocks are typed and MD040 is resolved.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-elaborating-scenarios/SKILL.md`:
- Line 4: The skill declares "Step 7 of Event Modeling - Elaborate scenarios
using Given-When-Then format." but other interview artifacts still say "Step 9",
causing sequencing mismatch; update all occurrences of the mismatched step label
so they are consistent (either change the header "Step 7" to "Step 9" or,
preferably, change the interview artifact labels "Step 9" to "Step 7") by
finding the strings "Step 7" and "Step 9" in SKILL.md (including the header and
the interview artifact blocks) and making them identical across the file.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md`:
- Line 396: Update the checklist line that currently reads "Automation marked
with gear symbols () to distinguish from user actions ()" to use explicit
markers instead of empty parentheses; replace the first empty placeholder with a
clear automation marker such as "[AUTO]" or "⚙️ [AUTO]" and the second with a
user marker like "[USER]" or "👤 [USER]" so the statement is unambiguous (locate
and edit the checklist text in SKILL.md where the phrase "Automation marked with
gear symbols () to distinguish from user actions ()" appears).
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-integrating-legacy-systems/SKILL.md`:
- Around line 174-209: Several fenced code blocks in SKILL.md lack language
identifiers; update each triple-backtick fence that contains prose (e.g., the
block starting "Traditional Approach (Risky):") to use a language tag such as
text or markdown, and annotate all code example fences (e.g., the JavaScript
snippet beginning "if (isNewFeature(request))") with the appropriate language
like javascript; apply this change consistently to the other omitted fences
mentioned in the review so markdownlint rule MD040 is satisfied.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/SKILL.md`:
- Around line 45-54: The markdown has untyped fenced code blocks that trigger
MD040; update each untyped fence that contains the decision checklist ("If user
has provided: ... Else: Conduct interview") to include a language tag such as
```text, and likewise tag the fenced block that begins with "## Interview
Findings: [Domain Name] Implementation Plan" with ```markdown (or ```md) so
markdownlint MD040 is satisfied; locate these blocks in SKILL.md by searching
for the exact checklist text and the "## Interview Findings: [Domain Name]
Implementation Plan" heading and add the appropriate language identifiers to the
opening backtick fences.
- Around line 106-108: The "When to Use" guidance in SKILL.md for the slicing
step currently references "Steps 1–7" which conflicts with the orchestrator's
9-step main flow; update the wording in the "When to Use" section (the "slicing"
guidance) to match the orchestrator's flow by either changing "Steps 1–7" to
"Steps 1–9" or by clarifying the exact point (e.g., "after completing the full
event model and before implementation") so the slicing step in SKILL.md aligns
with the orchestrator's 9-step main flow.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models/SKILL.md`:
- Around line 22-38: The fenced code blocks under the "VIOLATION EXAMPLE" and
"CORRECT PATTERN" sections (the blocks showing
ReviewAggregate/PublishReviewState/etc.) are untyped and causing markdownlint
MD040; update those fences to include a language identifier (for example ```text
or ```diff or ```txt) so the blocks are typed, and do the same for the other
untyped fence around the content referenced later (the block at the lines called
out in the review). Ensure both the violation and correct pattern blocks use
consistent language identifiers.
---
Duplicate comments:
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-elaborating-scenarios/SKILL.md`:
- Around line 404-530: The Markdown contains nested triple-backtick fences
(outer "```markdown" and inner "```gherkin") which breaks parsing; update the
outer fence to a 4-backtick fence (e.g., "````markdown" ... "````") or change
the inner Gherkin fences to a different fence style so they no longer use the
same backtick length—apply this around the Scenarios block containing "Command:
CreateOrder" / "ConfirmOrder" and the inner "```gherkin" examples so the outer
and inner fences are distinct and the file parses correctly.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/SKILL.md`:
- Around line 123-139: The formula and examples in the "Estimated Stream Length"
section mix incompatible time bases; update the formula to explicitly state two
variants—(Events per instance per year) × (Lifetime in years) × (Growth
multiplier) and alternatively (Total events per instance lifetime) × (Growth
multiplier)—and then revise each example to use one consistent basis: for
"E-commerce Order" state either "8 events total per order × 1.5 years lifetime =
8 total events" or convert to an annual rate before multiplying; for "Banking
Account" keep "100–200 per year × 10 years = 1000–2000" as is; for "Order
Processing" clarify whether "100+ per order" means per-year or total (if total,
present as total events × growth; if per-year, multiply by lifetime); for "SaaS
User" convert "1–5 per month" to annual (12–60 per year) before multiplying by 5
years to show 60–300 events, and ensure every example labels the units used (per
year or total).
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/references/project-planning-with-event-modeling.md`:
- Around line 171-173: The summary line "Result: All work done in ~22 weeks with
proper parallelization" contradicts the arithmetic and should be corrected to
reflect the parallelized calculation: compute 13 steps ÷ (3 teams × 3
steps/sprint) ≈ 1.44 sprints ≈ ~6 weeks and the non-parallelized case as 13
steps ÷ 3 steps/sprint ≈ 4.33 sprints ≈ ~17 weeks; update the "Result" sentence
and any adjacent explanatory text in project-planning-with-event-modeling.md to
show these corrected week estimates and ensure they match the table's 13 steps
and 3 steps/sprint assumptions.
- Line 125: The document has inconsistent sprint lengths: the phrase "Estimate:
9 ÷ 3 = 3 sprints = ~9 weeks" assumes 3-week sprints while the sprint mapping
table ("Week 1-4", etc.) uses 4-week sprints; choose one standard and make both
places match — either change the estimate text to use 4-week sprints (e.g.,
"Estimate: 9 ÷ 4 = 2.25 ≈ 3 sprints = ~12 weeks" or "Estimate: 9 ÷ 4 ≈ 2.25
sprints (~9 weeks of effort across 3 sprints if you keep 4-week sprints)") or
update the table entries ("Week 1-3", "Week 4-6", "Week 7-9") to reflect 3-week
sprints; update the specific strings "Estimate: 9 ÷ 3 = 3 sprints = ~9 weeks"
and the sprint-range rows ("Week 1-4", etc.) so they consistently reflect the
chosen sprint duration.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/examples.md`:
- Around line 166-167: The dependency matrix contradicts the slice definitions:
Slice 2 (Moderation) and Slice 3 (Responses) are declared "Can Run Parallel" and
Slice 3 only consumes ReviewPublished from Slice 1, so update the matrix
rows/columns for Responses (and symmetrically Ratings if applicable) to show no
dependency on Moderation (replace "← Depends" with "-" or "(self)" as
appropriate); alternatively, if Responses actually depends on Moderation, update
the Slice 2/3 descriptions and the consumed events list for Slice 3 to include
the relevant Moderation events so the matrix and slice definitions match (refer
to the symbols Responses, Ratings, Slice 2 (Moderation), and Slice 3 (Responses)
when making the change).
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-storyboarding-events/SKILL.md`:
- Around line 404-406: The markdown line currently combines the checklist item
"[ ] **System boundaries visible through swimlane organization**" and the
heading "## Key Principles" on one line; split them so the checklist item is its
own line and the "## Key Principles" heading is on the following line by moving
"## Key Principles" to a new line (ensure a blank line between list items and
the heading if needed) so the markdown renders correctly.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-translating-external-events/SKILL.md`:
- Around line 307-407: The top-level fenced block beginning with ```markdown
(the SKILL.md External Event Translation template) is closed prematurely by
inner fenced blocks (the ```json example under "Technical Representation" and
the triple-backtick block under "Translation Logic"); fix by replacing the outer
fence with a four-backtick fence (````markdown ... ````) or alternatively
convert the inner fenced examples to indented code blocks so the outer
```markdown remains intact—update the outer fence token around the "External
Event Translation: [Domain Name]" section or change the inner "```json" and the
inner triple-backtick in "Translation Logic" to indented blocks to prevent early
termination.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models-checklist/SKILL.md`:
- Line 4: The document's repeated "23 checks" claim is incorrect because the
enumerated validation phases (Phase 1..7 and Final Questions) only define 16
checks total; update every occurrence of the phrase "23 checks" in SKILL.md
(title/intro/body where "23 checks" appears) to "16 checks" and revise any
pass/fail criteria, summary statistics, or scoring logic that reference 23 to
use 16 instead so counts and thresholds remain consistent with the listed phases
(Phase 1:3, Phase 2:3, Phase 3:2, Phase 4:2, Phase 5:1, Phase 6:1, Phase 7:1,
Final Questions:3).
---
Nitpick comments:
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md`:
- Line 35: Multiple fenced code blocks in SKILL.md are missing language
identifiers and trigger markdownlint MD040; update each triple-backtick fence
for the flagged blocks by adding an appropriate language tag (e.g., ```text or
```markdown) immediately after the opening ``` so the examples and snippets are
lint-clean—apply this to every fenced block referenced (the ones at the reported
positions) and ensure the closing ``` remains unchanged.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-integrating-legacy-systems/SKILL.md`:
- Around line 164-165: The "Update Interview Trail" step is vague—explicitly
define the exact row shape that should be appended/updated so outputs match
orchestration artifacts: in SKILL.md update the "Update Interview Trail" section
to state the precise field names, types and required/optional flags (e.g.,
interview_id, timestamp, actor, action, payload) and include a concrete example
row/JSON object and a brief note that the orchestration expects this shape;
ensure any references to "Interview Trail" and the orchestration outputs mention
this schema and that implementers must adhere to it for consistent artifacts.
In
`@plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/patterns.md`:
- Line 36: Change the inconsistent heading "[COMMANDHANDLER]STATES INVOLVED:" in
patterns.md to match the other template headings; replace the
bracketed/run-together form (the exact token "[COMMANDHANDLER]STATES INVOLVED:")
with a consistent heading such as "COMMAND HANDLER STATES INVOLVED:" or simply
"States Involved:" so it follows the same capitalization and spacing style as
other sections.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: a7e294a3-41df-40ef-b527-b80fd08b5abb
📒 Files selected for processing (29)
.claude-plugin/marketplace.json.github/release-please-config.json.github/release-please-manifest.jsonplugins/trogonstack-eventmodeling/.claude-plugin/plugin.jsonplugins/trogonstack-eventmodeling/README.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-applying-conways-law/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-brainstorming-events/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-brainstorming-events/references/facilitating-event-modeling-workshops.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-checking-completeness/references/security-analysis-with-event-modeling.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-designing-event-models/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-elaborating-scenarios/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-outputs/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-integrating-legacy-systems/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/domain-patterns.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/patterns.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-optimizing-stream-design/references/snapshotting.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-orchestrating-event-modeling/references/project-planning-with-event-modeling.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-plotting-events/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/examples.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/references/patterns.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-storyboarding-events/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-translating-external-events/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models-checklist/SKILL.mdplugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models/SKILL.md
✅ Files skipped from review due to trivial changes (6)
- plugins/trogonstack-eventmodeling/README.md
- .github/release-please-config.json
- .github/release-please-manifest.json
- plugins/trogonstack-eventmodeling/.claude-plugin/plugin.json
- plugins/trogonstack-eventmodeling/skills/eventmodeling-plotting-events/SKILL.md
- plugins/trogonstack-eventmodeling/skills/eventmodeling-applying-conways-law/SKILL.md
🚧 Files skipped from review as they are similar to previous changes (1)
- .claude-plugin/marketplace.json
plugins/trogonstack-eventmodeling/skills/eventmodeling-brainstorming-events/SKILL.md
Outdated
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-designing-event-models/SKILL.md
Outdated
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-designing-event-models/SKILL.md
Outdated
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-elaborating-scenarios/SKILL.md
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-identifying-inputs/SKILL.md
Outdated
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-integrating-legacy-systems/SKILL.md
Outdated
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/SKILL.md
Outdated
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-slicing-event-models/SKILL.md
Show resolved
Hide resolved
plugins/trogonstack-eventmodeling/skills/eventmodeling-validating-event-models/SKILL.md
Outdated
Show resolved
Hide resolved
- Add event modeling plugin with 16 skills covering the full workflow - Apply skill authoring guide conventions across all skills - Prefix all skill names with eventmodeling- for namespace clarity - Improve skill effectiveness with orchestrator-first coordinator pattern - Fix YAML frontmatter block scalars, stale references, and quality checklists - Surface security analysis reference in checking-completeness skill - Align Conway's Law findings path with shared EVENTMODELING.md - Replace DDD aggregate language with event-sourcing projection terminology - Replace broad dual-write pattern with controlled mirror-write variant - Fix merged headings, duplicate headings, and missing code fence language tokens Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
trogonstack-eventmodelingplugin with 16 skills covering the complete Event Modeling methodology: brainstorm → plot → storyboard → identify inputs → identify outputs → apply Conway's Law → elaborate scenarios → check completeness → validate, plus dedicated skills for stream optimization, legacy system integration, model slicing, and an orchestrating skill that coordinates the full 9-step workflow with explicit gates between steps and mid-workflow entry supportallowed-tools, H1 titles,## Workflowsection naming, conditional interview phases with skip conditions, and quality checklists on every skillConfirmOrderState,ShipOrderState,CancelOrderStateinstead of the DDD anti-patternOrderAggregate), the slicing reference walkthrough, and the anti-pattern blocks in brainstorming, designing, and validating skills