code-review-excellence

Enforce AI-Commerce v2.0 architectural rules on pull requests with severity labels.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/jlpbiuma/agent-skills --skill code-review-excellence-jlpbiuma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-excellence
Source: https://github.com/jlpbiuma/agent-skills/tree/main/code-review-excellence
Command: npx skills add https://github.com/jlpbiuma/agent-skills --skill code-review-excellence-jlpbiuma

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the enforcement of strict architectural boundaries and coding standards within the AI-Commerce v2.0 platform, preventing common violations and ensuring code quality.

Core Features & Use Cases

  • Automated Architectural Guardrails: Checks for and flags violations of backend and frontend architectural rules.
  • Constructive Feedback: Provides clear, actionable feedback on pull requests, guiding developers towards compliance.
  • Use Case: When reviewing a pull request, this skill will automatically identify if a controller is attempting direct database access, prompting the developer to move the logic to the repository layer.

Quick Start

Use the code-review-excellence skill to review the attached pull request against architectural standards.

Frequently Asked Questions about code-review-excellence

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

FAQPage Schema
How do I automate code reviews to enforce backend architectural boundaries?

Backend architectural boundaries are enforced by automatically reviewing pull requests against the AI-Commerce v2.0 Architecture Decision Record, flagging violations like direct controller database access and impure entities with actionable feedback.

What is the best way to prevent frontend direct network requests in pull requests?

The best way to prevent frontend direct network requests is by applying automated architectural guardrails during code review, which identify boundary violations and provide constructive feedback to ensure compliance.

Can I use this code review enforcement for both frontend and backend pull requests?

Yes, you can use this code review enforcement for both frontend and backend pull requests. It identifies and flags distinct violations for each, such as fat routers and circular HTTP calls in the backend or direct network requests in the frontend.

Why does automated code review flag controllers attempting direct database access?

Automated code review flags controllers attempting direct database access because it violates architectural boundaries. The Skill identifies this issue and prompts developers to move the logic to the repository layer to maintain structural integrity.

What severity levels are used when flagging architectural violations in code reviews?

The severity levels used when flagging architectural violations in code reviews are [blocking], [important], and [nit]. These labels provide clear, constructive feedback to guide developers towards architectural compliance.