feat(trogonstack-eda): scaffold plugin for event-driven architecture skills#44
feat(trogonstack-eda): scaffold plugin for event-driven architecture skills#44
Conversation
PR SummaryLow Risk Overview Registers Reviewed by Cursor Bugbot for commit c2ea27e. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThis PR introduces the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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. Review rate limit: 0/1 reviews remaining, refill in 2 minutes and 51 seconds.Comment |
Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
54e70d5 to
bf85db1
Compare
Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
❌ 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 6108a72. Configure here.
Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
…ility Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
There was a problem hiding this comment.
🧹 Nitpick comments (1)
plugins/trogonstack-eda/skills/event-name/SKILL.md (1)
212-228: ⚡ Quick winConsider adding Rule 4 (CRUD) to the checklist.
The review checklist thoroughly covers 14 of the 15 rules, but Rule 4 ("No CRUD Unless CRUD IS the Domain") appears to be missing. While this is partially covered by checklist item 2 (domain language), Rule 4's nuanced guidance about when CRUD terms ARE appropriate (CMS, config management) might be worth including explicitly.
Suggested addition
After checklist item 5, add:
5. Naming format (PascalCase, dot.delimited, etc.) is consistent across the system +6. CRUD verbs (Created, Updated, Deleted) are only used when CRUD is the actual domain concept -6. Integration events are prefixed with bounded context or service name +7. Integration events are prefixed with bounded context or service name(and renumber subsequent items)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugins/trogonstack-eda/skills/event-name/SKILL.md` around lines 212 - 228, Add an explicit Rule 4 entry "No CRUD Unless CRUD IS the Domain" into the existing event-review checklist (insert after checklist item 5 as suggested) that explains avoid using CRUD terms unless the domain is actually CRUD (e.g., CMS/config management), and then renumber the subsequent items; update the checklist text near the list of 14 rules (the block starting with "When reviewing event definitions, verify:") to include this new rule and ensure numbering consistency.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@plugins/trogonstack-eda/skills/event-name/SKILL.md`:
- Around line 212-228: Add an explicit Rule 4 entry "No CRUD Unless CRUD IS the
Domain" into the existing event-review checklist (insert after checklist item 5
as suggested) that explains avoid using CRUD terms unless the domain is actually
CRUD (e.g., CMS/config management), and then renumber the subsequent items;
update the checklist text near the list of 14 rules (the block starting with
"When reviewing event definitions, verify:") to include this new rule and ensure
numbering consistency.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: b0a70003-c63b-45ac-a9f1-9284952119d7
📒 Files selected for processing (6)
.claude-plugin/marketplace.json.github/release-please-config.json.github/release-please-manifest.jsonplugins/trogonstack-eda/.claude-plugin/plugin.jsonplugins/trogonstack-eda/README.mdplugins/trogonstack-eda/skills/event-name/SKILL.md
…ness Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
… and collections Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
…re names, polymorphic payloads, and PII Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>

Summary
event-name,event-design-domain-schema,event-design-integration-schema,event-design-contract,event-audit-catalog