om-code-review

Review Open Mercato code for architectural, security, and quality issues.

6|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/SHGrowth/om-superpowers --skill om-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: om-code-review
Source: https://github.com/SHGrowth/om-superpowers/tree/main/skills/om-code-review
Command: npx skills add https://github.com/SHGrowth/om-superpowers --skill om-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviewers spend time ensuring OM code adheres to architecture, security, naming conventions, and quality standards. This skill provides structured review guidance and concrete findings to improve PRs.

Core Features & Use Cases

  • Module structure & conventions: checks for proper module layout, naming, and coding standards.
  • Security & quality gates: enforces security checks, data handling, and performance considerations.
  • PR audit outputs: generates categorized findings (Critical/High/Medium/Low) with actionable fixes.
  • Use case: When you open a PR, run this skill to produce a review report that you can attach to the PR.

Quick Start

Review the latest PR diff to verify architecture, security, naming conventions, and quality against OM standards.

Frequently Asked Questions about om-code-review

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

FAQPage Schema
How do I audit code for architecture and security gaps in a pull request?

You can audit code for architecture and security gaps by running an automated review against PR diffs and commits. This process enforces CI/CD gates, validates template parity, and outputs categorized findings with actionable fixes to attach to your pull request.

What is the best way to enforce module structure and naming conventions during code reviews?

The best way to enforce module structure and naming conventions during code reviews is to use an automated audit skill. It checks proper module layout, validates coding standards across frontend and backend boundaries, and flags anti-patterns before merging.

How does automated CI/CD code review handle unit and integration test coverage?

Automated CI/CD code review handles test coverage by validating unit and integration tests within the submitted diff. It checks patches across modules and services to ensure tests meet OM quality standards before merging the PR.

Can I use automated code review for diffs and patches across frontend and backend boundaries?

Yes, you can use automated code review for diffs and patches across frontend and backend boundaries. The review process identifies architectural deviations and validates that data handling and security checks meet standards across all service modules.

How do I generate a categorized findings checklist for code quality anti-patterns?

You generate a categorized findings checklist for code quality anti-patterns by running an automated audit on your commit or patch. The review outputs structured findings categorized by severity—Critical, High, Medium, or Low—each accompanied by actionable fixes.