Review C# ABP Framework code for DDD principles and anti-patterns.
npx skills add https://github.com/j7-dev/everything-github-copilot --skill abp-reviewer
Please help me install this Agent Skill. Skill: abp-reviewer Source: https://github.com/j7-dev/everything-github-copilot/tree/main/skills/abp-reviewer Command: npx skills add https://github.com/j7-dev/everything-github-copilot --skill abp-reviewer
This Skill acts as an expert code reviewer for C# projects built with the ABP Framework, ensuring adherence to best practices, DDD principles, and ABP-specific patterns.
Review the provided C# code snippet for adherence to ABP Framework best practices.
High-intent search queries and answers about installing and using this skill.
To review C# code for ABP Framework anti-patterns, submit your snippet for analysis to identify domain logic encapsulation issues and repository misuse before deployment.
Common multi-tenancy implementation issues involve incorrect tenant isolation and domain entity configuration. Expert review detects these flaws to ensure adherence to ABP best practices.
To check if Application Services follow ABP DDD principles, analyze the code against ABP 9.x patterns to verify correct separation of concerns and CQRS implementation.
Yes, this reviewer supports ABP 9.x modularity and CQRS analysis. It evaluates your module system configurations and command-query separations to enforce structural best practices.
Your ABP repository usage violates DDD principles when data access logic leaks into application services. Code review pinpoints these anti-patterns to enforce proper domain layer encapsulation.
afonsoftAutomate ABP CLI workflows for proxy generation, library installation, and module operations.
afonsoftAutomate ABP feature workflows for entities, migrations, services, localization, permissions, and tests.
MassimilianoPiliImplements backend services with C# and ASP.NET Core 9+ including APIs, EF Core migrations, LINQ queries, xUnit tests, ProblemDetails, and DI.
LuizEduPPModels backend architecture to separate domain, use case, and adapter layers.
