mbc-review

Identify anti-patterns and best-practice violations in MBC CQRS Serverless codebases.

29|5|Updated Dec 21, 2023
One-click install
npx skills add https://github.com/mbc-net/mbc-cqrs-serverless --skill mbc-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mbc-review
Source: https://github.com/mbc-net/mbc-cqrs-serverless/tree/main/packages/mcp-server/skills/mbc-review
Command: npx skills add https://github.com/mbc-net/mbc-cqrs-serverless --skill mbc-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams review code written with the MBC CQRS Serverless framework to prevent common implementation mistakes and anti-patterns that lead to multi-tenant data bugs, incorrect DynamoDB usage, broken tracing/auditability, or event/data consistency issues.

Core Features & Use Cases

  • Anti-pattern detection & guidance: Flags risky patterns (for example around tenantCode handling, publishAsync vs publishSync, pagination, and error logging) and explains why they are wrong.
  • Detector-to-guideline mapping: Provides a cross-reference so that when an automated anti-pattern detector reports a code, reviewers can jump to the matching, human-focused guidance and fixes.
  • Review checklist for MBC architecture: Covers module wiring, service/controller conventions, DTO validation and Swagger documentation, and DataSyncHandler/event-emission correctness.

Quick Start

Ask the reviewer skill to review your MBC CQRS Serverless codebase with the goal of identifying anti-patterns, mapping any detected AP codes to this guide, and producing prioritized issues with suggested fixes.

Frequently Asked Questions about mbc-review

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

FAQPage Schema
How do I review CQRS serverless code for multi-tenancy and DynamoDB anti-patterns?

Review CQRS serverless code by mapping detected anti-pattern codes to specific guidance sections for multi-tenancy key handling, DynamoDB usage, and event sourcing. This produces prioritized findings with suggested fixes to prevent data consistency and tracing issues.

What are common event sourcing anti-patterns in CQRS serverless architectures?

Common event sourcing anti-patterns include incorrect publishAsync vs publishSync usage, broken DataSyncHandler event-emission design, and improper tenantCode handling. These violations lead to incorrect auditability, broken tracing, and multi-tenant data bugs.

How does a code review checklist handle DTO validation and Swagger documentation in serverless CQRS?

A code review checklist handles DTO validation and Swagger documentation by checking service and controller conventions within the MBC CQRS framework. It flags missing validation rules and incomplete API documentation as actionable findings.

Does this code review approach work with AWS DynamoDB and event sourcing patterns?

Yes, this code review approach works with AWS DynamoDB and event sourcing patterns. It specifically evaluates CommandService and DataService usage, ensuring correct DynamoDB interactions and validating event-emission design for data consistency.

What's the best way to fix multi-tenant data bugs in CQRS frameworks before deployment?

The best way to fix multi-tenant data bugs in CQRS frameworks is to run a targeted code review that identifies risky tenantCode handling patterns. It maps these anti-patterns to specific guidance and produces prioritized issues with suggested fixes.

Why does my CQRS serverless code have broken tracing and event consistency issues?

CQRS serverless code often has broken tracing and event consistency issues due to incorrect error handling, improper publishAsync usage, and flawed DataSyncHandler design. A specialized code review identifies these specific anti-patterns and their fixes.