zenticalab-pr-review

Analyze ZENTICALAB pull requests against specs and quality standards.

19|2|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/CamiloAndresGTRUniandes/lucy-ai --skill zenticalab-pr-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zenticalab-pr-review
Source: https://github.com/CamiloAndresGTRUniandes/lucy-ai/tree/main/skills/zenticalab-pr-review
Command: npx skills add https://github.com/CamiloAndresGTRUniandes/lucy-ai --skill zenticalab-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you perform consistent, production-grade pull request reviews for ZENTICALAB repositories by catching spec mismatches, security weaknesses, and architecture/testing regressions before merge.

Core Features & Use Cases

  • Comprehensive PR review workflow: Summarizes PR intent, scopes review to changed files, and validates implementation against spec.md and related HU.
  • Security, architecture, and testing guardrails: Provides backend (.NET/.NET Clean Architecture, multi-tenancy) and frontend (Angular 21, standalone components, signals, Tailwind v4) checklists.
  • Structured reviewer output: Produces an actionable review message with clear Summary, Approve/Request Changes/Needs Discussion, and Blocking Issues.
  • Multi-tenancy-specific validation: Flags cross-tenant data leak risks (schema-per-tenant enforcement, tenant context correctness, migrations idempotency).

Quick Start

Use the zenticalab-pr-review skill when reviewing a ZENTICALAB pull request to generate a checklist-driven review that includes Security, Testing, and clearly labeled Blocking Issues with file-level references.

Frequently Asked Questions about zenticalab-pr-review

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

FAQPage Schema
How do I review a .NET backend pull request for Clean Architecture and multi-tenancy issues?

Review a .NET backend pull request by validating changed files against acceptance criteria, enforcing Clean Architecture boundaries, and checking schema-per-tenant enforcement to prevent cross-tenant data leaks. The review output explicitly flags blocking issues with file-level references.

What is the best way to check an Angular frontend PR for UI conventions and security gaps?

Check an Angular frontend PR by applying a checklist that validates standalone components, signals, and Tailwind v4 UI conventions alongside security guardrails. This generates an actionable review message labeling blocking issues and required changes.

Does this pull request review workflow support validating specs and testing expectations?

Yes, the pull request review workflow supports validating specs by summarizing PR intent and comparing implementation against spec.md and related HU. It also enforces testing expectations to catch architecture and testing regressions before merge.

How do I enforce security checklists and tenant-aware validation rules during code review?

Enforce security checklists and tenant-aware validation rules during code review by applying a structured workflow that flags tenant context correctness, migration idempotency, and cross-tenant data leak risks. It produces a security architecture performance code-quality checklist output.

Can I use this to generate a structured PR review message with blocking issues?

Yes, you can generate a structured PR review message that includes a clear summary, an Approve/Request Changes/Needs Discussion verdict, and explicitly labeled Blocking Issues with file-level references to ensure production-grade quality standards.