review-code

Reviews code for quality, security, performance, accessibility, and DaaS compliance with severity-rated findings.

Updated May 27, 2026
One-click install
npx skills add https://github.com/Rkaaaa404/cyberhack-SYDT --skill review-code-rkaaaa404
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-code
Source: https://github.com/Rkaaaa404/cyberhack-SYDT/tree/main/.agents/skills/review-code
Command: npx skills add https://github.com/Rkaaaa404/cyberhack-SYDT --skill review-code-rkaaaa404

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual code reviews are inconsistent and often miss security vulnerabilities, performance anti-patterns, or platform-specific compliance rules. This Skill standardizes the review process by checking code against a structured multi-dimensional checklist and producing actionable, severity-rated feedback. ## Core Features & Use Cases - Multi-Dimensional Review: Checks correctness, security, DaaS/Buildpad compliance, performance, accessibility, and test coverage in one pass. - Severity-Rated Output: Classifies every finding as CRITICAL, WARNING, or INFO with exact file locations and concrete fix recommendations. - Platform Compliance Enforcement: Verifies Buildpad-first component usage, API proxy patterns, and auth routing rules specific to DaaS applications. - Use Case: Before merging a pull request for a Next.js feature, run the review to catch missing Zod validation on API handlers, direct Supabase client calls, or unstable useEffect dependencies. ## Quick Start Ask the assistant to review the code in a specific file or feature, for example by saying review the dispatch API route for security and performance issues.

Frequently Asked Questions about review-code

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

FAQPage Schema
How do I review code for security vulnerabilities before merging a PR?▼

Run the review-code skill on the target file or feature to check for exposed secrets, missing auth checks on API routes, absent Zod input validation, and unsafe direct Supabase client calls. Findings are reported with severity levels and exact file locations.

What does a code review checklist for Next.js and Supabase apps include?▼

The checklist covers correctness, security, performance, accessibility, testing, and DaaS/Buildpad compliance. It verifies proxy-pattern API routing, auth through /api/auth routes, Buildpad component usage, and stable useEffect dependencies.

How are code review findings prioritized by severity?▼

Each finding is labeled CRITICAL (must fix), WARNING (should fix), or INFO (consider). Every entry includes the category, file path with line number, and a specific fix recommendation.

Can this review check Buildpad and DaaS platform compliance rules?▼

Yes, it enforces the Buildpad-first rule against raw Mantine components, requires all API calls through /api proxy routes, and verifies business logic lives in DaaS extensions rather than Next.js API routes.

What are the limitations of an automated checklist-based code review?▼

Checklist reviews catch known pattern violations but cannot judge architectural fit or business logic intent. Complex design decisions and domain-specific correctness still require human reviewer judgment.