code-review

Review code changes for compliance with Open Mercato's architecture, security, and quality rules.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/drshk5/erp_sales --skill code-review-drshk5
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/drshk5/erp_sales/tree/main/.ai/skills/code-review
Command: npx skills add https://github.com/drshk5/erp_sales --skill code-review-drshk5

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code changes against established architectural, security, and quality standards, ensuring consistency and reducing manual review overhead.

Core Features & Use Cases

  • Automated Code Auditing: Scans code changes for violations of architecture, security, naming conventions, and quality rules.
  • Actionable Findings: Provides categorized, severity-based feedback with specific fix suggestions.
  • Use Case: When a developer submits a pull request, this Skill can automatically flag potential issues related to tenant isolation, input validation, or adherence to module structure before a human reviewer even looks at it.

Quick Start

Use the code-review skill to review the changes in the current pull request.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code review for a pull request?

Automated code review scans pull requests for violations of architecture, security, naming conventions, and quality rules. It identifies issues across module structure, data security, and UI patterns to provide actionable findings before human review.

What is architecture compliance checking in code changes?

Architecture compliance checking validates code changes against established module structure and event rules. It flags anti-patterns and convention violations using a detailed checklist, ensuring code changes maintain structural integrity and consistency.

Can I check naming conventions and module structure in a diff?

Yes, you can check naming conventions and module structure in a diff. The review process evaluates code changes against specific rules, identifying structural violations and providing categorized feedback with fix suggestions.

What's the best way to flag anti-patterns before a human reviewer looks at my code?

The best way to flag anti-patterns is using a severity-based code review checklist. This automatically detects violations across cache, queue, and UI rules, generating actionable feedback for developers to resolve issues proactively.

When do I need an automated quality assurance scan for my commits?

You need an automated quality assurance scan when submitting commits to ensure consistency and reduce manual overhead. It checks for adherence to architecture, security, and quality rules, catching violations early in the development cycle.